|
From: Nicholas N. <n.n...@gm...> - 2009-01-19 08:57:11
|
On Mon, Jan 19, 2009 at 7:49 PM, Tom Hughes <to...@co...> wrote: > Nicholas Nethercote wrote: > >> I discovered that on Darwin, DWARF debug info doesn't get put into >> executables. Rather, if you do something like this: >> >> gcc -g a.c >> >> Then alongside the created executable 'a.out', a directory called >> 'a.out.dSYM' is made, and it holds the debug info. Greg's patch looks >> for such directories when loading debuginfo. >> >> However, if you do the compilation in two steps: >> >> gcc -g -c a.c >> gcc -g a.o >> >> then the .dSYM directory is not created. Rather, you have to do an >> additional step to create it: >> >> dsymutil a.out > > That's quite bizarre though, as it means the data must be present in the > executable if dsymutil can extract it to the separate directory? AIUI the debug info is in the .o files, and the .o files can be found from the executable. See http://wiki.dwarfstd.org/index.php?title=Apple's_"Lazy"_DWARF_Scheme N |