Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Daniel Berlin <dberlin@dberlin.org>
Cc: Jason Molenda <jason-swarelist@molenda.com>,
	Daniel Jacobowitz <drow@false.org>,
	Nick Savoiu <savoiu@ics.uci.edu>,
	gdb@sources.redhat.com
Subject: Re: Debugging a large program
Date: Mon, 11 Oct 2004 06:10:00 -0000	[thread overview]
Message-ID: <4169E5CF.4070201@gnu.org> (raw)
In-Reply-To: <Pine.LNX.4.60.0410092352150.19081@dberlin.org>

> 
>>
>> Andrew's approach is much cooler,

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

I remember the mmap stuff but not much else.
At one stage I ran the basics past Jim but he didn't mention your stuff 
(just described it has hard to impossible).  Do you have a URL.

>> GDB needs to find ways to achieve (assuming co-operation from GCC and 
>> BFD) an initial:
>> 
>> - process symtab sections (for address ranges) - O(<nr sections>)
>> 
>> and then when a symbol is requested:
>> 
>> - lookup symbol - O(log (<nr symbols>)) * O(<nr solibs>) for first time 
>> (better?); O(1) for re-searches

Right now, I think this is the most important aspect.  It establishes an 
absolute bound on the performance.  No matter what is done, it needs to 
be measured against that.

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

Andrew



  reply	other threads:[~2004-10-11  1:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <F51E79B1-195C-11D9-ACAD-000A9569836A@gnu.org>
2004-10-08 21:35 ` Jason Molenda
2004-10-11  1:46   ` Daniel Berlin
2004-10-11  6:10     ` Andrew Cagney [this message]
2004-10-11 13:59   ` Andrew Cagney
2004-10-04 21:15 Nick Savoiu
2004-10-04 21:16 ` Daniel Jacobowitz
2004-10-04 23:21   ` Daniel Jacobowitz
2004-10-04 23:25     ` Nick Savoiu
2004-10-05  5:24       ` Daniel Jacobowitz
2004-10-05 15:26         ` Nick Savoiu
  -- strict thread matches above, loose matches on Subject: below --
2004-10-04 20:48 Nick Savoiu
2004-10-04 20:54 ` Daniel Jacobowitz
2004-10-05 14:05   ` Andrew Cagney
2004-10-05 14:07     ` Daniel Jacobowitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4169E5CF.4070201@gnu.org \
    --to=cagney@gnu.org \
    --cc=dberlin@dberlin.org \
    --cc=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=jason-swarelist@molenda.com \
    --cc=savoiu@ics.uci.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox