On Sat, Sep 20, 2014 at 08:33:01AM +0100, Andrew Haley wrote: > On 20/09/14 02:45, Ian Grant wrote: > > > You get first prize for most informative intelligent answer so far! > > Careful, you might get second prize too :-) > > > > The problem is that we need to find a way to tell people _what_ is in > > that "dwarf" code. Open BSD's gcc ignores it, prints a warning, and > > goes about its business. That's probably why OpenBSD gcc 4.9 binaries > > are 17MB against the 64MB compiled by gcc 4.9. But that is a really > > fucking big dwarf they're stuffing in threre. What is the data, > > really? We can't just say "it's dwarf" because that doesn't really > > mean a whole lot, does it? > > It's debugging information for debuggers. What more are you asking > for? Do you need to know about the structure of the debuginfo, or > something?
And if you need that, it is easily available, see http://www.dwarfstd.org/ https://fedorahosted.org/elfutils/wiki/DwarfExtensions . If you care only about what matters for execution of the generated binaries, it is only the allocated sections that matter (with A flag in readelf -WS output), and all the debug info is in non-allocated sections only. Jakub
