From: Kip Macy <kip.macy@gmail.com>
To: Mark Williamson <mark.williamson@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: policies on coredump
Date: Wed, 27 Apr 2005 17:57:11 -0700 [thread overview]
Message-ID: <b1fa291705042717576982b142@mail.gmail.com> (raw)
In-Reply-To: <200504280143.59630.mark.williamson@cl.cam.ac.uk>
My plan is for coredump to write out the domain state in a generic
format and then post-process that into the format expected by the
kernel GDB for a given OS. I can envision using the suspend support
for offline state inspection by simply post-processing the output of
suspend to disk into coredump format. I don't see anyone else
clamoring to use xen as a development environment so I'll worry about
that later.
-Kip
On 4/27/05, Mark Williamson <mark.williamson@cl.cam.ac.uk> wrote:
> > If it is in the reap path is there any reason to add it to xm as well
> > other than testing?
>
> I guess that now, for most things, you could use the gdbserver to poke at the
> state of domains that hadn't crashed (and auto-dumped) yet... Under some
> circumstances it might be useful to manually dump domain state for later
> analysis.
>
> Unless anybody pipes up and asks then I guess it might not be worth adding.
> It's probably worth getting the reap-path patch into the tree in the first
> instance - then other people can contribute patches to enable any use cases
> they want ;-)
>
> Cheers,
> Mark
>
prev parent reply other threads:[~2005-04-28 0:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-27 23:22 policies on coredump Kip Macy
2005-04-27 23:47 ` Mark Williamson
2005-04-28 0:34 ` Kip Macy
2005-04-28 0:43 ` Mark Williamson
2005-04-28 0:57 ` Kip Macy [this message]
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=b1fa291705042717576982b142@mail.gmail.com \
--to=kip.macy@gmail.com \
--cc=mark.williamson@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
/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.