From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JuNyv-0000fm-S3 for qemu-devel@nongnu.org; Fri, 09 May 2008 04:29:33 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JuNyu-0000fS-DS for qemu-devel@nongnu.org; Fri, 09 May 2008 04:29:33 -0400 Received: from [199.232.76.173] (port=54523 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JuNyt-0000fP-UW for qemu-devel@nongnu.org; Fri, 09 May 2008 04:29:32 -0400 Received: from gecko.sbs.de ([194.138.37.40]:18335) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1JuNyt-0006ra-CT for qemu-devel@nongnu.org; Fri, 09 May 2008 04:29:31 -0400 Received: from mail2.sbs.de (localhost [127.0.0.1]) by gecko.sbs.de (8.12.11.20060308/8.12.11) with ESMTP id m498T3Vx009243 for ; Fri, 9 May 2008 10:29:03 +0200 Received: from [139.25.109.167] (mchn012c.mchp.siemens.de [139.25.109.167] (may be forged)) by mail2.sbs.de (8.12.11.20060308/8.12.11) with ESMTP id m498T3Hl027694 for ; Fri, 9 May 2008 10:29:03 +0200 Message-ID: <48240B4E.2060309@siemens.com> Date: Fri, 09 May 2008 10:29:02 +0200 From: Jan Kiszka MIME-Version: 1.0 Subject: Re: [Qemu-devel] Debugging vmlinux with qemu and gdb. Unable to step, next, print or to get any information.. References: <824D057211107844BA95DB341B4BF12E01139BF2@hanvsmail04.eu.thmulti.com> <4823D56F.1010600@windriver.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit 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 Mulyadi Santosa wrote: > HI Jason... > > On Fri, May 9, 2008 at 11:39 AM, Jason Wessel > wrote: >>> Of course, this assume that there is no bugs while Qemu inspect and >>> found that it must pause at certain address... I believe Jasson Wessel >>> had squashed all that kind of bugs in the past. >>> >>> regards, >>> >>> Mulyadi. >>> >>> >> I believe that Mulyadi is talking about the following two patches which >> are attached here, assuming you are able to hit breakpoints. > > Thanks.... I believe that's the patch that will fix his problem. I'm not /that/ sure. The second one affects single stepping only, and the first one is now redundant as QEMU (and thus also KVM) uses a compacter way of supporting x86-64 registers. But maybe the patch is still required for "old" QEMU 0.9.1 (I'm working with development heads only). But IIRC, the error pattern used to be quite different when QEMU did not yet support x86-64 registers. Jan -- Siemens AG, Corporate Technology, CT SE 2 Corporate Competence Center Embedded Linux