public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "dje at google dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/13511] 'info variable' and 'info functions' very slow and memory cosuming
Date: Wed, 11 Jan 2012 20:26:00 -0000	[thread overview]
Message-ID: <bug-13511-4717-I64OEbbbbI@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13511-4717@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=13511

dje at google dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ccoutant at google dot com,
                   |                            |dje at google dot com

--- Comment #1 from dje at google dot com 2012-01-11 20:25:51 UTC ---
gdb does full symtab expansion here which will use a lot of debug info.

One thought is to have enough information to be able to avoid that.
E.g., could .gdb_index include enough info to avoid having to do full symtab
expansion? [that also has problems, but "info var|fun|type" is common enough
that triggering an explosion of debug info reading is annoying and worth
avoiding]
[and similarly for psymtabs, as well as maybe enhancing pubnames/pubtypes]

Another thought is to be more selective with debug info reading.
Is it possible to read only the parts of the CU (dwarf-speak) that we need?

Another thought is to throw out the info as we're finished using it, perhaps
guided by various parameters.
[we'll have to read it again, but that's preferable to bringing a machine to a
crawl]

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  reply	other threads:[~2012-01-11 20:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-16 17:11 [Bug symtab/13511] New: " andre.poenitz at nokia dot com
2012-01-11 20:26 ` dje at google dot com [this message]
2023-03-06 23:50 ` [Bug symtab/13511] " tromey at sourceware dot org

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=bug-13511-4717-I64OEbbbbI@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).