Re: [Xen-devel] [PATCH] mkelf32: Correct sh_link

[Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>]

On 3/1/07 8:11 pm, "John Levon" <levon@xxxxxxxxxxxxxxxxx> wrote:

>> That would potentially be nice, but I don't know of any tools that would
>> allow us to symbolically debug a dump without having a separate source of
>> symbol information (like xen-syms).
> 
> This is exactly what is available on Solaris both for userspace core
> dumps and kernel crash dumps. We'd like to be able to extend this to
> Xen. As far as I know, there's nothing preventing, say, Red Hat's
> 'crash' doing the same.

Well, extracting symbols from the existing Xen format isn't hard. We could
add that, but really it's not as good as source-level debugging, being able
look at local variables up the call stack, etc. I don't think it is
expecting much to require xen-syms to be kept around for xen images that are
still being tested. Another trick might be to allow production of a xen
image with the full xen-syms image appended -- then a crash dump would have
all the info required to do full source-level debugging (except the source
tree, but you do get a changeset number from the core dump which will
suffice if you use revision control). That would be easy actually -- just
get mkelf32 to append the xen-syms file and set a couple of values at a
known offset in the main xen image, easily picked up by crashdump tools and
by Xen itself.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel