From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Christoph Egger" Subject: Re: [PATCH] mkelf32: Correct sh_link Date: Thu, 4 Jan 2007 09:30:51 +0100 Message-ID: <200701040930.51259.Christoph.Egger@amd.com> References: <20070103183605.GA32102@totally.trollied.org.uk> <20070103192031.GA1115@totally.trollied.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20070103192031.GA1115@totally.trollied.org.uk> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com Cc: John Levon List-Id: xen-devel@lists.xenproject.org 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