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: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] [PATCH] mkelf32: Correct sh_link
From: "Christoph Egger" <Christoph.Egger@xxxxxxx>
Date: Thu, 4 Jan 2007 09:30:51 +0100
Cc: John Levon <levon@xxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 04 Jan 2007 00:34:02 -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>
Organization: AMD / OSRC
References: <20070103183605.GA32102@xxxxxxxxxxxxxxxxxxxxxxx> <C1C1B127.46F4%Keir.Fraser@xxxxxxxxxxxx> <20070103192031.GA1115@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.4
On Wednesday 03 January 2007 20:20, John Levon wrote:
> On Wed, Jan 03, 2007 at 07:14:47PM +0000, Keir Fraser wrote:
> > >> What we have now works and produces a reasonably compressed symbol
> > >> table. I don't see any value in changing it.
> > >
> > > It seems like it would simplify things. And it would certainly help us
> > > as we want to ship the binary with (compressed) debug info, which is
> > > tricky right now due to this unusual behaviour...
> >
> > 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.

Further, when you boot on a serial console how do you connect gdb
over a serial console? You can't use a serial console for two things
concurrently. Then a xen-kernel debugger is useful. And yeah, that needs
standard symtabs and strtabs.
And with a kernel debugger, you don't need to worry about what John pointed
out.

regards,
John



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