From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Dvdpo-0003Sy-Ch for qemu-devel@nongnu.org; Thu, 21 Jul 2005 12:23:44 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Dvdpm-0003SF-8r for qemu-devel@nongnu.org; Thu, 21 Jul 2005 12:23:43 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Dvdpl-0003Q0-Kp for qemu-devel@nongnu.org; Thu, 21 Jul 2005 12:23:41 -0400 Received: from [81.103.221.48] (helo=mta08-winn.ispmail.ntl.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1Dvdto-00053A-KC for qemu-devel@nongnu.org; Thu, 21 Jul 2005 12:27:52 -0400 From: Julian Seward Subject: Re: [Qemu-devel] Network code on AMD64 Date: Thu, 21 Jul 2005 17:18:13 +0100 References: <20050721123232.7bf2456c@nim.leo> <20050721152543.GA4122@jbrown.mylinuxbox.org> In-Reply-To: <20050721152543.GA4122@jbrown.mylinuxbox.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200507211718.13858.jseward@acm.org> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: "Jim C. Brown" > > 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