public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "xdje42 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/17681] Huge memory leak when using tab completion
Date: Sun, 07 Dec 2014 18:55:00 -0000	[thread overview]
Message-ID: <bug-17681-4717-sesFptys5g@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17681-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=17681

Doug Evans <xdje42 at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |xdje42 at gmail dot com

--- Comment #1 from Doug Evans <xdje42 at gmail dot com> ---
I suspect this is not a "leak" per se, but rather just gdb's horrendously bad
support for tab-completion.

The hypothesis is that gdb is reading and expanding all debug information -->
boom.
The "-", I think, triggers a search for all symbols.

There is a patch in the works to limit the damage.
https://sourceware.org/ml/gdb-patches/2014-11/msg00685.html
Beyond that, there is still more gdb can do to be smarter here, but at least
memory usage won't explode.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  reply	other threads:[~2014-12-07 18:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-05 16:15 [Bug gdb/17681] New: " hadess at hadess dot net
2014-12-07 18:55 ` xdje42 at gmail dot com [this message]
2014-12-07 22:00 ` [Bug gdb/17681] " hadess at hadess dot net
2015-01-05 19:12 ` [Bug gdb/17681] Tab completion needs better throttling dje at google dot com
2022-04-08  2:04 ` 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-17681-4717-sesFptys5g@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).