https://sourceware.org/bugzilla/show_bug.cgi?id=18616
--- Comment #8 from Nick Clifton <nickc at redhat dot com> --- (In reply to Marco Leise from comment #7) [Sorry for the long delay in responding...] > I am actually using a git checkout past 2.30 right now and the issue is > still present. Darn. > What is the command line you use for objdump? objdump -W <file> > I.e. is there a > way to make it print source lines for symbols as oprofile would? objdump -WL <file> I doubt if this is the same as oprofile will produce, but both tools will be displaying processed DWARF line number information so they should be roughly equivalent. You can also use "objdump -Wl <file>" (with a lowercase-l rather than an uppercase-L) to see the raw DWARF debug line information. Cheers Nick -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
