From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: dave.anderson@redhat.com, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] Kernel core dumps from qemu
Date: Wed, 25 Mar 2009 00:32:33 +0000 [thread overview]
Message-ID: <200903250032.34889.paul@codesourcery.com> (raw)
In-Reply-To: <49C921A6.3070202@redhat.com>
> This looks useful. I'd suggest a 'format' argument, so we can extend
> this later to dump in non-ELF formats (the Windows native memory dump
> format would be useful).
I'm not keen on having a plethora of different formats in qemu, especially if
they are proprietary or poorly documented. As long as it's done properly it
should be straight forwarded to reconstruct everything else (vritual
addresses, other formats) with offline debug tools.
What you actually want to do is use the the existing snapshot/savevm
mechanism, and postprocess that into whatever format you want.
Paul
next prev parent reply other threads:[~2009-03-25 0:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 16:54 [Qemu-devel] Kernel core dumps from qemu Chris Smith
2009-03-24 18:08 ` Avi Kivity
2009-03-24 20:19 ` Chris Smith
2009-03-25 9:41 ` Avi Kivity
2009-03-25 0:32 ` Paul Brook [this message]
2009-03-25 9:28 ` Avi Kivity
2009-03-25 18:02 ` Chris Smith
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=200903250032.34889.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=avi@redhat.com \
--cc=dave.anderson@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.