From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:48938) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WlDmA-0001NJ-Kh for qemu-devel@nongnu.org; Fri, 16 May 2014 04:46:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WlDm3-0000rB-5E for qemu-devel@nongnu.org; Fri, 16 May 2014 04:45:58 -0400 Received: from cantor2.suse.de ([195.135.220.15]:59296 helo=mx2.suse.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WlDm2-0000qw-UK for qemu-devel@nongnu.org; Fri, 16 May 2014 04:45:51 -0400 Message-ID: <5375D03C.50906@suse.de> Date: Fri, 16 May 2014 10:45:48 +0200 From: =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= MIME-Version: 1.0 References: <20140516090322.78f174a3@bahia.local> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] dump-guest-memory command? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jun Koi Cc: "qemu-devel@nongnu.org" , Greg Kurz Am 16.05.2014 10:40, schrieb Jun Koi: > What I want > to know is how to map 0x12345 (virtual address) back to the dump file. >=20 > For example, if 0x12345 was executing some filesystem code at the time = I > dumped the VM, then I can locate exactly that code in the dumpfile, > thanks to the given RIP address (which is 0x12345 in this example) >=20 > I hope I explain my idea clear enough this time? Using dump-guest-memory sounds more complicated than needed. You can just use the monitor commands for disassembling that address or the built-in gdb stub (-s). Regards, Andreas --=20 SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=C3=BCrnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend=C3=B6rffer; HRB 16746 AG N=C3=BC= rnberg