Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@zwingli.cygnus.com>
To: Daniel Berlin <dan@cgsoftware.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: PATCH: fail to improve psymtab memory consumption
Date: Fri, 20 Jul 2001 22:22:00 -0000	[thread overview]
Message-ID: <nppuausvng.fsf@zwingli.cygnus.com> (raw)
In-Reply-To: <87lmljdz4g.fsf@cgsoftware.com>

Daniel Berlin <dan@cgsoftware.com> writes:
> Hence the reason I only read the part of the various sections for a
> given CU (rather than reading the entire section).

Yeah, I think that's the way to go.  The 12Mb of .debug_info,
.debug_abbrev, and .debug_line data lying there is the biggest issue.
There's no reason we couldn't read it in for partial symbol table
construction, throw it away when we're done, and then bring in data
for only those CU's we need, only when we need it.

GNU malloc uses mmap for big chunks of data, so when you free a big
block of memory (like debug_info_buffer) after doing the partial
symbol scan, the memory really does go back to the system; it doesn't
just get added to malloc's free list.

> I actually use mmap when possible, but that's for speed, rather than
> memory savings.

Is it really faster?

> It doesn't buy us anything if we still mmap the entire section, and
> then touch every part. :)

Which we do when in building the partial symbol table.


  reply	other threads:[~2001-07-20 22:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010720212013.7DA695E9D8@zwingli.cygnus.com>
2001-07-20 15:17 ` Daniel Berlin
2001-07-20 22:22   ` Jim Blandy [this message]
2001-07-20 23:17     ` Daniel Berlin
2001-07-21  8:50       ` Jim Blandy
2001-07-23 20:36       ` Andrew Cagney
2001-07-23 22:15         ` Daniel Berlin
2001-07-24  7:49           ` Andrew Cagney
2001-07-24  9:47             ` Daniel Berlin
2001-07-24  9:16           ` Kevin Buettner
2001-07-24  9:35             ` Christopher Faylor
2001-07-24 10:13               ` Frank Ch. Eigler
2001-07-24 10:57                 ` Christopher Faylor

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=nppuausvng.fsf@zwingli.cygnus.com \
    --to=jimb@zwingli.cygnus.com \
    --cc=dan@cgsoftware.com \
    --cc=gdb-patches@sources.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