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

[John Levon <levon@xxxxxxxxxxxxxxxxx>]

On Wed, Jan 03, 2007 at 08:06:12PM +0000, Keir Fraser wrote:

> > Indeed, and that's what we're doing currently. But this is problematic
> > as it's very easy for other files to get lost, not be handed over etc.
> > and working backwards to the right version is very rarely feasible...
> > Thus we'd like to have a single binary (or more importantly dump!) that
> > has everything in place.
> 
> 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.

> The problems you mention would typically
> be resolved by non-technical means anyway (offical release builds for which
> you keep a copy of the bits, which can then be used to augment the
> information from a raw dump).

Bitter experience tends to show this doesn't work well especially in
development environments.

> I wouldn't deep-dive into a core dump for a
> build of dubious heritage where the builder hadn't kept the sources and
> build bits! :-)

All too common alas :) Wasting a small amount of time debugging a dodgy
build is usually better than letting a real intermittent bug slip by...

regards,
john

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