Closed GoogleCodeExporter closed 9 years ago
Please give r1422 or newer a try. It should be fixed.
Original comment by thestig@chromium.org
on 5 Feb 2015 at 11:07
This fixes the issue I originally described, but on closer inspection things
are still broken.
I created a very simple test program and compared the results of nm and
dump_syms on two builds, one with embedded symbols and another with linked
symbols. The results:
nm symbols_test -l | wc -l
37
nm symbols_test_linked -l | wc -l
37
dump_syms symbols_test | wc -l
46
dump_syms symbols_test_linked | wc -l
29
Both dump_syms and nm produce correct results for the binary with embedded
symbols. But when given a file with linked symbols, dump_syms doesn't output
any FILE or FUNC data. That's why its output is 17 lines shorter.
nm output is identical for both files.
Original comment by tom.edwa...@thefoundry.co.uk
on 6 Feb 2015 at 11:02
Given symbols_test_linked, and the debugging symbols for symbols_test_linked as
/path/to/foo/symbols_test_linked.debug, you need to run:
dump_syms symbols_test_linked /path/to/foo
The .gnudebuglink section in symbols_test_linked only contains a file name and
checksum. You need to pass the directories to search to dump_syms.
Original comment by thestig@chromium.org
on 6 Feb 2015 at 11:53
Gets me every time! dump_syms really ought to automatically handle symbols
being in the same directory as the binary...
This bug is fixed.
Original comment by tom.edwa...@thefoundry.co.uk
on 9 Feb 2015 at 10:26
For /path/to/file, it looks like gdb tries:
- /path/to/file.debug
- /path/to/.debug/file.debug
- /usr/lib/debug/path/to/file.debug
I suppose dump_syms can do the same.
Original comment by thestig@chromium.org
on 9 Feb 2015 at 7:43
Original issue reported on code.google.com by
tom.edwa...@thefoundry.co.uk
on 14 Jan 2015 at 12:07Attachments: