qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Jun Koi <junkoi2004@gmail.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Greg Kurz <gkurz@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] dump-guest-memory command?
Date: Fri, 16 May 2014 10:45:48 +0200	[thread overview]
Message-ID: <5375D03C.50906@suse.de> (raw)
In-Reply-To: <CA+g7VZ0dPtXaK0u7toHFk5Rqc_u=pdCfLLbLW41jLTAsNYKEww@mail.gmail.com>

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.
> 
> 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)
> 
> 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

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2014-05-16  8:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-16  6:24 [Qemu-devel] dump-guest-memory command? Jun Koi
2014-05-16  7:03 ` Greg Kurz
2014-05-16  8:40   ` Jun Koi
2014-05-16  8:45     ` Andreas Färber [this message]
2014-05-16  8:51       ` Jun Koi
2014-05-16 10:00         ` Greg Kurz
2014-05-16  9:51     ` Greg Kurz
2014-05-16  9:59       ` Jun Koi
2014-05-16 10:15         ` Greg Kurz
2014-05-16 11:30         ` Laszlo Ersek
2014-05-16 13:01           ` Jun Koi
2014-05-16 15:38             ` Laszlo Ersek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5375D03C.50906@suse.de \
    --to=afaerber@suse.de \
    --cc=gkurz@linux.vnet.ibm.com \
    --cc=junkoi2004@gmail.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).