From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DvdVo-0002lv-SJ for qemu-devel@nongnu.org; Thu, 21 Jul 2005 12:03:04 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DvdVk-0002kd-V9 for qemu-devel@nongnu.org; Thu, 21 Jul 2005 12:03:04 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DvdVV-0002Cg-46 for qemu-devel@nongnu.org; Thu, 21 Jul 2005 12:02:45 -0400 Received: from [128.8.10.164] (helo=po2.wam.umd.edu) by monty-python.gnu.org with esmtp (Exim 4.34) id 1Dvd5K-0001Wb-R4 for qemu-devel@nongnu.org; Thu, 21 Jul 2005 11:35:42 -0400 Received: from jbrown.mylinuxbox.org (jma-box.student.umd.edu [129.2.237.180]) by po2.wam.umd.edu (8.12.10/8.12.10) with ESMTP id j6LFPhjD021354 for ; Thu, 21 Jul 2005 11:25:43 -0400 (EDT) Date: Thu, 21 Jul 2005 11:25:43 -0400 From: "Jim C. Brown" Subject: Re: [Qemu-devel] Network code on AMD64 Message-ID: <20050721152543.GA4122@jbrown.mylinuxbox.org> References: <20050721123232.7bf2456c@nim.leo> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <20050721123232.7bf2456c@nim.leo> 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 On Thu, Jul 21, 2005 at 12:32:32PM +0100, Paul LeoNerd Evans wrote: > Apologies if this issue has already been solved, by the way; I've only > just joined the mailing list... >=20 No, this problem has come up a couple times but until now no one has actual= ly tried to fix them. Good job. > But there's a problem. Currently my only test image is a Windows 98SE > install - not best known for being able to properly debug - I shall have > to test with a decent Knoppix or something like that... But I find that > if I start up IE, it attempts a connection to its default homepage, then > Qemu itself segfaults. Normally I'd fire up gdb at this stage and have a > good look around, but I gather from documentation that the internals of > qemu are far from standard, and I might be somewhat out of my depth here. >=20 qemu does a lot of strange things, but the hardware emulation code (e.g. the code that emulates the ne2k) as well as the servers emulation code (e.g. the code that emulates a dhcp server or the code that handles the proxying of t= cp/ip requests) can easily be debugged using gdb. I've done it many times myself = - only the translated machine code itself can not be viewed this way (for obvious reasons). > I thought I'd report here anyway; maybe someone with more development > experience could pick it up, or at least, give me some suggestions of > tests to run. I'm quite familiar with C in general, and Linux coding, but > I've never done anything like the dynamic translation stuff that qemu is > doing here... >=20 Odds are good this isn't the place where the segfault is occuring, and like= I said the rest of qemu is perfectly debuggable in gdb. --=20 Infinite complexity begets infinite beauty. Infinite precision begets infinite perfection.