From: Julian Seward <jseward@acm.org>
To: qemu-devel@nongnu.org
Cc: "Jim C. Brown" <jma5@umd.edu>
Subject: Re: [Qemu-devel] Network code on AMD64
Date: Thu, 21 Jul 2005 17:18:13 +0100 [thread overview]
Message-ID: <200507211718.13858.jseward@acm.org> (raw)
In-Reply-To: <20050721152543.GA4122@jbrown.mylinuxbox.org>
> > Qemu itself segfaults. Normally I'd fire up gdb at this stage and have a
> > good look around,
Why don't you fire up Valgrind and have a good look around? It can
find all manner of bad stuff that GDB doesn't find, like out-of-
bounds memory accesses and use of uninitialised values that are often
the root causes of segfaults. At least, that's what lots of Valgrind
users tell us :-) Recent Valgrinds should be able to run QEMU-softmmu
variants.
J
next prev parent reply other threads:[~2005-07-21 16:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-21 11:32 [Qemu-devel] Network code on AMD64 Paul LeoNerd Evans
2005-07-21 15:25 ` Jim C. Brown
2005-07-21 16:18 ` Julian Seward [this message]
2005-07-21 21:55 ` Paul LeoNerd Evans
2005-07-21 22:58 ` Paul LeoNerd Evans
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200507211718.13858.jseward@acm.org \
--to=jseward@acm.org \
--cc=jma5@umd.edu \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).