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? Andrew.
