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