[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] xm dump-core and analyzing

  • To: "Keir Fraser" <keir@xxxxxxxxxxxxx>
  • From: "David Pilger" <pilger.david@xxxxxxxxx>
  • Date: Tue, 12 Dec 2006 08:15:22 +0200
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Dave Anderson <anderson@xxxxxxxxxx>
  • Delivery-date: Mon, 11 Dec 2006 22:15:14 -0800
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=aaOKGaHffkWzTGXHw010IoFlE2OpGAHKYPej85vagBShXzUHRh1nF7cZp0S4l7+rI/r8ykmZEnaabr4egpIsSEKG27D0zH2pH0ezNdBh8hXyV47SyBKqwuNieaxyADaIbgKxH3+G5B3ADg9V4loe2L79Por+gYUdm+ViSR21F+s=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On 12/11/06, Keir Fraser <keir@xxxxxxxxxxxxx> wrote:
The current format is an ancient, non-extensible and largely
unmaintained hack;

For the extensibility part, may I suggest that you turn
coredump_header.xch_nr_vcpus length into 16 bits and use the other 16
bits that left as an offset for a new header (PE style). I don't know
how old software will handle xch_nr_vcpus > 64K, as it always dumps
just the context for the first CPU.

But I understood that you are going to work on an ELF dump format...
good luck with that, it is surely needed!

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.