Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Berlin <dberlin@dberlin.org>
To: Jim Blandy <jimb@redhat.com>
Cc: david carlton <carlton@math.stanford.edu>, <gdb@sources.redhat.com>
Subject: Re: suggestion for dictionary representation
Date: Tue, 24 Sep 2002 06:19:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0209240917300.11838-100000@dberlin.org> (raw)
In-Reply-To: <200209240635.g8O6ZUC23979@zenia.red-bean.com>



On Tue, 24 Sep 2002, Jim Blandy wrote:

> 
> > Also, for what it's worth, I'm still not ready to completely give up
> > on representing members of classes via a dictionary; that would
> > provide another place where a linear dictionary environment could be
> > useful.
> 
> I agree, but it's worth noting that `struct symbol' is 52 bytes long
> on a Pentium, whereas `struct field' and `struct fn_field' are 16
> bytes long.  
> 
> Not that that necessarily matters.  We know GDB does have memory
> consumption problems, but I have never seen those problems really
> analyzed. 

Um, I have these statistics, but I need to know *exactly* what you want to 
know to be able to give them to you.
There's just too many combinations to make a nice table or something.
Even something like STABS vs DWARF2 has too many combinations because 
it changes with each GCC version, and even sometimes with binutils 
versions.

> All the memory could be in physnames, for all we know. 
In general, DWARF2 C++ apps, a lot of it is.

--Dan


  reply	other threads:[~2002-09-24 13:19 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-23 23:50 Jim Blandy
2002-09-24  6:19 ` Daniel Berlin [this message]
2002-09-24  7:06   ` Daniel Jacobowitz
2002-09-24 21:01   ` Jim Blandy
2002-09-25  5:54     ` Daniel Jacobowitz
2002-09-27 11:23       ` Jim Blandy
2002-09-27 11:28         ` Daniel Jacobowitz
2002-09-24  9:49 ` David Carlton
  -- strict thread matches above, loose matches on Subject: below --
2002-09-22 19:59 Jim Blandy
2002-09-22 20:11 ` Daniel Jacobowitz
2002-09-23 10:38   ` David Carlton
2002-09-23 17:34     ` Daniel Berlin
2002-09-23 18:39       ` Daniel Jacobowitz
2002-09-23 21:28         ` Daniel Berlin
2002-09-23 21:38           ` Eli Zaretskii
2002-09-23 21:44             ` Daniel Berlin
2002-09-23 21:47               ` Eli Zaretskii
2002-09-23 21:54                 ` Daniel Berlin
2002-09-24  9:33       ` David Carlton
2002-09-24 10:42         ` Daniel Berlin
2002-09-24 10:53           ` David Carlton
2002-09-24 20:01         ` Jim Blandy
2002-09-24 20:50           ` Daniel Berlin
2002-09-23 18:28     ` Daniel Jacobowitz
2002-09-24  3:51     ` Paul N. Hilfinger
2002-09-24 19:52     ` Jim Blandy
2002-09-24 20:37       ` Elena Zannoni
2002-09-24 20:53       ` Daniel Berlin

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=Pine.LNX.4.44.0209240917300.11838-100000@dberlin.org \
    --to=dberlin@dberlin.org \
    --cc=carlton@math.stanford.edu \
    --cc=gdb@sources.redhat.com \
    --cc=jimb@redhat.com \
    /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