public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "jakub at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/14636] New: Tab completion issues in C++ Date: Thu, 27 Sep 2012 19:56:00 -0000 [thread overview] Message-ID: <bug-14636-4717@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=14636 Bug #: 14636 Summary: Tab completion issues in C++ Product: gdb Version: 7.5 Status: NEW Severity: normal Priority: P2 Component: gdb AssignedTo: unassigned@sourceware.org ReportedBy: jakub@redhat.com Classification: Unclassified cat > a.ii <<\EOF # 1 "a.C" # 1 "a1.h" 1 struct basic_block_def; typedef basic_block_def *basic_block; # 2 "a.C" 2 # 1 "a2.h" 1 struct basic_block_def { int index; }; # 3 "a.C" 2 __attribute__((noinline, noclone)) static void foo (basic_block x, int y) { __asm volatile ("" : : : "memory"); } int main () { foo ((basic_block) 0, 0); } EOF g++ -g -o a a.ii gdb ./a p foo<tab> This will print just (gdb) p foo(basic_block and stop there, even when the function isn't overloaded, and further tab is about just completing the basic_block word, not the whole function name. I don't care much which equivalent typedef is chosen in the tab completion, but would prefer if just one of them (slight preference might be what is used in the sources if there is just one alternative). -- 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.
next reply other threads:[~2012-09-27 19:56 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-09-27 19:56 jakub at redhat dot com [this message] 2012-09-28 10:52 ` [Bug gdb/14636] " jan.kratochvil at redhat dot com 2014-02-14 15:35 ` gbenson at redhat dot com 2023-12-31 15:05 ` ssbssa 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-14636-4717@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: linkBe 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).