From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: save lots of memory
Date: Thu, 05 Nov 2009 17:28:00 -0000 [thread overview]
Message-ID: <20091105172839.GI4557@adacore.com> (raw)
In-Reply-To: <m3ljil228l.fsf@fleche.redhat.com>
> This patch changes gdb so that such names are not copied. This saves a
> lot of memory. For example, I ran OO.o writer and attached to it with
> gdb (I have full debug info installed for OO.o and all its
> dependencies).
As discussed on IRC, I looked at the patch, and I think it is pretty
nice. The downside for the other formats seems reasonably small and
we have the options suggested by Tom in case we need to reclaim
the extra memory being consumed with the current approach.
I'm looking forward to measuring the impact on memory and performance
with one of the bigger apps we have in house :-).
--
Joel
next prev parent reply other threads:[~2009-11-05 17:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-05 1:24 Tom Tromey
2009-11-05 17:28 ` Joel Brobecker [this message]
2009-12-27 3:40 ` Joel Brobecker
2009-11-05 19:59 ` Daniel Jacobowitz
2009-11-06 18:20 ` Tom Tromey
2009-11-06 19:23 ` Paul Pluzhnikov
2009-11-06 20:50 ` Tom Tromey
2009-11-16 18:41 ` Tom Tromey
2009-11-16 22:14 ` Tom Tromey
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=20091105172839.GI4557@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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