All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Anderson <anderson@redhat.com>
To: xen-devel@lists.xensource.com
Subject: Re:  xm dump-core and analyzing
Date: Mon, 11 Dec 2006 10:34:09 -0500	[thread overview]
Message-ID: <457D7A71.8E86AE2D@redhat.com> (raw)
In-Reply-To: E1Gtma9-0003cb-Qr@host-192-168-0-1-bcn-london

>
>
>
>
> Hi Akio, Thanks for your help.
>
> But I don't think this tool is compatible with xm dump-core's product,
> but rather with xen0/xenU kernel coredumps.
>
> Anyone?
>

The xm dump-core facility is just a way of forcing a xenU crash,
and uses the same dumpfile format as xenU kernel coredumps.

Xen0 coredumps require the kdump facility since xen0 needs to
be running in order to take a xenU coredump.

Anyway, the crash utility supports xendumps from paravirtualized
x86 and x86_64 xenU kernels, and vmcores from the currently
under development xen0-kdump facility.

Dave Anderson


>
> On 12/11/06, Akio Takebe <takebe_akio@jp.fujitsu.com> wrote:
> > Hi, David
> >
> > Yes, you can use crash utility.
> > See the below.
> >     http://people.redhat.com/anderson
> >
> > Best Regards,
> >
> > Akio Takebe
> >
> > >Hi,
> > >
> > >Is there any tool out there that can help me analyze a coredump?
> > >
> > >Thanks,
> > >David.
> > >

       reply	other threads:[~2006-12-11 15:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1Gtma9-0003cb-Qr@host-192-168-0-1-bcn-london>
2006-12-11 15:34 ` Dave Anderson [this message]
2006-12-11 15:48   ` xm dump-core and analyzing Keir Fraser
2006-12-11 15:59     ` Dave Anderson
2006-12-11 16:10       ` Keir Fraser
2006-12-11 16:47         ` Dave Anderson
2006-12-11 23:55           ` John Levon
2006-12-12 13:42             ` Dave Anderson
2006-12-12  6:15         ` David Pilger
2006-12-12 12:20           ` John Levon
2006-12-12 13:52             ` David Pilger
2006-12-11 23:48     ` John Levon
2006-12-11 13:10 David Pilger
2006-12-11 13:22 ` Akio Takebe
2006-12-11 14:55   ` David Pilger

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=457D7A71.8E86AE2D@redhat.com \
    --to=anderson@redhat.com \
    --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.