|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] [PATCH] mkelf32: Correct sh_link
On 3/1/07 6:36 pm, "John Levon" <levon@xxxxxxxxxxxxxxxxx> 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). What exactly is your requirement?
-- Keir
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] [PATCH] mkelf32: Correct sh_link, Christoph Egger
- Re: [Xen-devel] [PATCH] mkelf32: Correct sh_link, Keir Fraser
- Re: [Xen-devel] [PATCH] mkelf32: Correct sh_link, Christoph Egger
- Re: [Xen-devel] [PATCH] mkelf32: Correct sh_link, Keir Fraser
- Re: [Xen-devel] [PATCH] mkelf32: Correct sh_link, Christoph Egger
- Re: [Xen-devel] [PATCH] mkelf32: Correct sh_link, Keir Fraser
- Re: [Xen-devel] [PATCH] mkelf32: Correct sh_link, John Levon
- Re: [Xen-devel] [PATCH] mkelf32: Correct sh_link,
Keir Fraser <=
- Re: [Xen-devel] [PATCH] mkelf32: Correct sh_link, John Levon
- Re: [Xen-devel] [PATCH] mkelf32: Correct sh_link, Keir Fraser
- Re: [Xen-devel] [PATCH] mkelf32: Correct sh_link, John Levon
- Re: [Xen-devel] [PATCH] mkelf32: Correct sh_link, Keir Fraser
- Re: [Xen-devel] [PATCH] mkelf32: Correct sh_link, John Levon
- Re: [Xen-devel] [PATCH] mkelf32: Correct sh_link, Keir Fraser
- Re: [Xen-devel] [PATCH] mkelf32: Correct sh_link, John Levon
- Re: [Xen-devel] [PATCH] mkelf32: Correct sh_link, Christoph Egger
- Re: [Xen-devel] [PATCH] mkelf32: Correct sh_link, Keir Fraser
- Re: [Xen-devel] [PATCH] mkelf32: Correct sh_link, Christoph Egger
|
|
|
|
|