Re: objdump, 64-bit objects and Solaris kernel modules

[Gabriel Marin <mgabi at cs dot rice dot edu>]

Did you compile your binary with -g -xs ?
Without the -xs option the compiler will not include the debug info in the
binary, but only in the object files. dbx knows how to search for it in the
object files, but for you it is better if you specify -xs.
Anyway, I did not verify for 64-bit binaries, but if they use stabs format I
.. hope it should work.

Gabriel


Steve Madsen wrote:

> Gabriel Marin wrote:
> > The problem is not limited at 64-bit binaries. I had this problem with
> > 32-bit binaries.
>
> I applied your patch to the latest from CVS this morning and it does not
> fix the problem for me on 64-bit binaries.
>
> It appears that my version of Forte is using different names for the
> STABS debugging sections than expected by
> _bfd_stab_section_find_nearest_line.  That functions looks for .stab and
> stabstr, and if not found, assumes that the object contains no
> debugging info and exits.
>
> Forte generates the following STABS sections in my object:
>
> 6 .stab.index   00000114 0000000000000000 0000000000000000 000025b0 2**2
>                  CONTENTS, READONLY, DEBUGGING
> 7 .stab.indexstr 00000320 0000000000000000 0000000000000000 000026c4 2**0
>                  CONTENTS, READONLY, DEBUGGING
> 8 .stab.excl    0000765c 0000000000000000 0000000000000000 000029e4 2**2
>                  CONTENTS, READONLY, DEBUGGING
> 9 .stab.exclstr 0001bfa1 0000000000000000 0000000000000000 0000a040 2**0
>                  CONTENTS, READONLY, DEBUGGING
>
> --
> Steve Madsen <madsen@tadpole.com>
> Tadpole Computer, Inc.  http://www.tadpole.com