Re: Debugging a large program

[Daniel Berlin <dberlin@dberlin.org>]

>
> Andrew's approach is much cooler,

Which is probably why i suggested exactly that years ago :)

The cooperation you need is a bit more than just debug_pubnames, pubtypes, 
and debug_aranges though (so that info functions and whatnot still worked 
like it does now), but nobody has ever asked any gcc guys to implement it 
for them (heck, i'd be happy to if you guys put together a definitive list 
of things you need, and proposed any new sections to the dwarf3 mailing 
list).

If you don't care about info functions output, tab completion of names, or 
are willing to live with them only showing "public" symbols, i believe you 
could implement this stuff now.

bfd's window stuff is currently undefined unless want_mmap is set to true 
(by the configure option --with-mmap, the default is false, it seems).
You need that to be able to just get pieces of the section.

It looks like it has a non-mmap fallback implemented in bfdwin.c, but 
"bfd_generic_get_section_contents_in_window" aborts if you don't have 
USE_MMAP set.

So uh, just wake me someone gets all the bfd stuff sorted out, and 
you guys figure out what you need more than what you've got to do 
this in the way you want it done, and i'll happily help propose these 
things on the dwarf3 reflector/implement them for gcc.

--Dan