bfd Mach-O DWARF debugging support
Sun Apr 8 10:07:00 GMT 2012
It seems that the binary references to `.o` files. That is also where
`dsymutil` is collecting its debug info from.
Apples GDB and other Apple tools read this referenced debug info.
Maybe libbfd should too?
On Fri, Apr 6, 2012 at 5:13 AM, Albert Zeyer <firstname.lastname@example.org> wrote:
> I was wondering about the current state of the Mach-O DWARF debugging
> support. I saw some patches recently which implemented
> `bfd_mach_o_find_nearest_line` (that is mostly what I am interested
> I have a binary which was build via `gcc -gdwarf-2` (Apples GCC).
> I tried binutils-2.22.52 but it doesn't really work for me. I tried to
> debug it a bit. Some things I can say so far:
> * `objdump -g` doesn't output anything regarding debugging info.
> * In bfd/dwarf2.c, in find_line(), _bfd_dwarf2_slurp_debug_info returns false.
> * In _bfd_dwarf2_slurp_debug_info(), find_debug_info returns false.
> * `objdump -h` doesn't list any debug section.
> When I use `dsymutil` to generate a dSYM from my binary,
> `bfd_mach_o_find_nearest_line` works.
> Can somebody give some hints wether it should work or about the current state?
More information about the Binutils