From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JuVcl-00031I-Tv for qemu-devel@nongnu.org; Fri, 09 May 2008 12:39:11 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JuVcj-00030a-P2 for qemu-devel@nongnu.org; Fri, 09 May 2008 12:39:11 -0400 Received: from [199.232.76.173] (port=40753 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JuVcj-00030W-Jd for qemu-devel@nongnu.org; Fri, 09 May 2008 12:39:09 -0400 Received: from nan.false.org ([208.75.86.248]:59884) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JuVci-0001hy-US for qemu-devel@nongnu.org; Fri, 09 May 2008 12:39:09 -0400 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 0ABAD983EA for ; Fri, 9 May 2008 16:39:08 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id E658598371 for ; Fri, 9 May 2008 16:39:07 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1JuVch-0001xg-6D for qemu-devel@nongnu.org; Fri, 09 May 2008 12:39:07 -0400 Date: Fri, 9 May 2008 12:39:07 -0400 From: Daniel Jacobowitz Subject: Re: [Qemu-devel] Debugging vmlinux with qemu and gdb. Unable to step, next, print or to get any information.. Message-ID: <20080509163907.GA7514@caradoc.them.org> References: <824D057211107844BA95DB341B4BF12E01139BF2@hanvsmail04.eu.thmulti.com> <4823D56F.1010600@windriver.com> <20080509144029.GA32414@caradoc.them.org> <482463F7.3050407@windriver.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <482463F7.3050407@windriver.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 On Fri, May 09, 2008 at 09:47:19AM -0500, Jason Wessel wrote: > Because you mentioned it though I'll have a look. I seem to recall there > was some kind of encoding for monitor packets which should be straight > forward enough. Right. GDB just hex encodes everything after the word "monitor" and passes it to the target. -- Daniel Jacobowitz CodeSourcery