This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

meaning of this objdump output?


The output of objdump -t is documented to be "similar to the information
provided by the `nm' program."  Except that it isn't.  Reading through
the code, '-t' forwards to bfd_print_symbol(), which is a macro wrapper
around something horrible.  :-)  That's where I gave up.

For example,

    47% nm -C libstdc++.so | grep S_free_list
    0009d640 B std::__default_alloc_template<true, 0>::_S_free_list
    48%

nm's documentation explains to me (and more importantly, my coworkers!) what
the B means.  No problems there, nm is a common tool.

But this output

    49% objdump -t -C -j .bss libstdc++.so | grep _S_free_list
    0009d640 g     O .bss   00000080              std::__de[ trim long name ]
    50%

isn't similar, doesn't correspond, and isn't documented.  My coworkers
could figure out the address field (obvious), and the ".bss" and "00000080"
fields were obvious to me, but none of us can tell what the "g" and "O" are.

Anyone give us a hand?


Thanks for your time,
Phil

-- 
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace.  We seek
not your counsel, nor your arms.  Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen.            - Samuel Adams


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]