From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EpIpm-0003cA-B2 for qemu-devel@nongnu.org; Thu, 22 Dec 2005 00:17:46 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EpIpk-0003by-R9 for qemu-devel@nongnu.org; Thu, 22 Dec 2005 00:17:46 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EpIpk-0003bv-NZ for qemu-devel@nongnu.org; Thu, 22 Dec 2005 00:17:44 -0500 Received: from [64.233.182.202] (helo=nproxy.gmail.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1EpIoo-0005M5-M3 for qemu-devel@nongnu.org; Thu, 22 Dec 2005 00:16:46 -0500 Received: by nproxy.gmail.com with SMTP id c2so114378nfe for ; Wed, 21 Dec 2005 21:16:42 -0800 (PST) Message-ID: <92c265230512212116l7d86f5dtf90784ba0d75c1c4@mail.gmail.com> Date: Thu, 22 Dec 2005 13:16:41 +0800 From: Tace Subject: Re: [Qemu-devel] Problems with gdbserver and debugging In-Reply-To: <16af12af0512211843h2c73e20v72ec61d150eb13d7@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <16af12af0512211843h2c73e20v72ec61d150eb13d7@mail.gmail.com> 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 Hi, I might have similar problems to what you just described. Mine's is when my kernel module causes several oops, the gdbserver will no longer break on the breakpoint in virtual machine. I have no idea why this occurs and Fabrice hasn't reply to my mail yet... On 12/22/05, Andre Pech wrote: > Hi, > > I'm running into problems using qemu to debug a kernel module. My host a= nd > virtual machine are both x86 running Fedora Core 4. After insmoding the > module in the virtual machine, starting gdbserver, running gdb on the hos= t > with the module sections loaded at the right place, and setting a breakpo= int > in the module code, gdb does not always get notified when the code is > exectuted. After adding debugging statements to qemu, I've experienced th= e > following two different failure cases: > > 1) The breakpoint is set, but > translate.c:gen_intermediate_code_internal is not being > called for the breakpoint address. If I understand things correctly, this > suggests that the translation block invalidation code which is executed e= ach > time a breakpoint is set has a problem in it. > > 2) translate.c:gen_intermetiate_code_internal is called on > the address where the breakpoint is set, and gen_debug is called. However= , > gdb does not break into the code. With DEBUG_GDB set, you can see that th= e > gdbstub code isn't doing anything in this case, so the gdb process i am > running is never notified that the breakpoint was hit. > > Both of these cases occur frequently, but not every time. I can run gdb, > have it break correctly, kill gdb (after disabling the breakpoint and > continuing), then start gdb again and have it fail. > > I'm going to keep trying to debug this, but I was hoping that someone mi= ght > have some insight into what is going on here. I have not upgraded to qemu > 0.8.0 yet, but i couldn't find anything that suggested that this would fi= x > the problem. Has anyone else run into similar problems? > > Thanks > Andre Pech > > _______________________________________________ > Qemu-devel mailing list > Qemu-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/qemu-devel > > >