WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

To: John Levon <levon@xxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] mkelf32: Correct sh_link
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Wed, 03 Jan 2007 20:06:12 +0000
Cc: Christoph Egger <Christoph.Egger@xxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 03 Jan 2007 12:05:55 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070103192031.GA1115@xxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Accvcp2W3HL+EZtlEduRSgAKle7CWA==
Thread-topic: [Xen-devel] [PATCH] mkelf32: Correct sh_link
User-agent: Microsoft-Entourage/11.2.5.060620
On 3/1/07 7:20 pm, "John Levon" <levon@xxxxxxxxxxxxxxxxx> wrote:

>> You can ship xen-syms if users want extra debug info (e.g., attach a gdb
>> client).
> 
> 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). 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). 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! :-)

 -- Keir



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