objdump -S omits source when input uses .gnu

objdump -S omits source when input uses .gnu_debuglink

Andreas Schwab schwab@suse.de
Fri Jun 22 12:24:00 GMT 2007

Previous message (by thread): objdump -S omits source when input uses .gnu_debuglink
Next message (by thread): objdump -S omits source when input uses .gnu_debuglink
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Nick Clifton <nickc@redhat.com> writes:

> Hi Noah,
>
>> When an object's debugging information resides in a separate file, linked via a
>> .gnu_debuglink section, `objdump -S' does not show source code; the output is
>> rigorously identical to that of `objdump -d'.
>
> Hmm, this was not quite as straightforward as I would have hoped, but I
> think there is a way to do it.  Please could you try out the attached
> patch and let me know if it works for you.

This does not work with a separate debug directory.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, MaxfeldstraÃŸe 5, 90409 NÃ¼rnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Previous message (by thread): objdump -S omits source when input uses .gnu_debuglink
Next message (by thread): objdump -S omits source when input uses .gnu_debuglink
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the Binutils mailing list