public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "k04jg02 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/11526] GDB thinks every type is a a possibility for tab completion on template arguments
Date: Wed, 21 Apr 2010 17:30:00 -0000	[thread overview]
Message-ID: <20100421173048.29901.qmail@sourceware.org> (raw)
In-Reply-To: <20100421151540.11526.k04jg02@gmail.com>


------- Additional Comments From k04jg02 at gmail dot com  2010-04-21 17:30 -------
Thinking about this a little more, it's theoretically possible that a future
shared library load could contain a new instantiation, and you may want to break
on that instantiation before the library loads. But that's not the common case.
Even when that does happen it'll probably be an instantiation on a type internal
to that shared library that isn't loaded yet either. But the current behavior
isn't useful at all even for trivial programs that specify few types (including
any standard header, like iostream, will likely bring in a ton of types). So I
think it would be best if tab completion only showed instantiations that are
actually available, but gdb still had the behavior of letting you type in
unloaded symbols to break on in a future shared library load.

-- 


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

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  reply	other threads:[~2010-04-21 17:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-21 15:15 [Bug c++/11526] New: " k04jg02 at gmail dot com
2010-04-21 17:30 ` k04jg02 at gmail dot com [this message]
2010-04-29 20:59 ` [Bug c++/11526] " swagiaal at redhat dot com
     [not found] <bug-11526-4717@http.sourceware.org/bugzilla/>
2011-06-01 13:08 ` timp at pulsic dot com

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=20100421173048.29901.qmail@sourceware.org \
    --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).