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

Re: [Xen-devel] [PATCH] Improve guest stack traces

  • To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
  • From: Kip Macy <kip.macy@xxxxxxxxx>
  • Date: Sat, 14 Jan 2006 01:51:50 -0800
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, John Levon <john.levon@xxxxxxx>
  • Delivery-date: Sat, 14 Jan 2006 09:58:41 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:references; b=UhAtyq9gcVlxrIR/5jusnKsezdoL8pA3mhN8dLhCGnAjtsFvbTWZjTbIDtRj1Py8Lq7NO97Os7MB2woYaO+KCFxUlcNqEvEPMMNfmBdeHUVqxw3iFDKEbNahWlxLaoM17sy7k3BVK/uqhRtqTMkdAZfjlOkyPYRqxX9jhr3vKuY=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

And if you're using a compiler that generates symbols that gdb supports, you can get a *lot* more info by using gdb + gdbserver. Writing a script to wrap execing those two and dumping a crashed VMs state would be a fairly trivial exercise.


On 1/14/06, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote:

On 13 Jan 2006, at 23:13, John Levon wrote:

> Add an option to use the frame pointer for guest stack traces.
> For stack dumps, avoid assumptions regarding stack size, and
> continue past unreadable addresses, which helps when a guest
> has overflowed its stack.
> Signed-off-by: John Levon <john.levon@xxxxxxx>

Improved guest backtraces belong in the xenctx utility
(tools/xentrace/xenctx.c). It already has the clear advantage that it
can print kernel symbols as well as addresses. The stack dump code in
Xen is mainly for very early crashes in dom0, and it's quite sufficient
for that.

So, if you want a frame-walking mode, put it in xenctx.

  -- Keir

Xen-devel mailing list

Xen-devel mailing list



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