From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [PATCH] mkelf32: Correct sh_link Date: Thu, 04 Jan 2007 09:58:51 +0000 Message-ID: References: <200701040930.51259.Christoph.Egger@amd.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200701040930.51259.Christoph.Egger@amd.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Christoph Egger , xen-devel@lists.xensource.com Cc: John Levon List-Id: xen-devel@lists.xenproject.org On 4/1/07 08:30, "Christoph Egger" 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. > > 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. Gdbstub and console can share a serial port. When gdbstub is entered then the gdbstub steals the serial port. Console messages are then wrapped as gdb messages. Given that this setup works and requires minimal code in Xen, I have no interest in accepting an in-kernel debugger into the tree. -- Keir