public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "pmuldoon at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug cli/15548] New: Limit completions to a pre-defined limit when completions list is very large Date: Wed, 29 May 2013 11:39:00 -0000 [thread overview] Message-ID: <bug-15548-4717@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=15548 Bug ID: 15548 Summary: Limit completions to a pre-defined limit when completions list is very large Product: gdb Version: unknown Status: NEW Severity: enhancement Priority: P2 Component: cli Assignee: unassigned at sourceware dot org Reporter: pmuldoon at redhat dot com Related: http://sourceware.org/bugzilla/show_bug.cgi?id=9007 When you complete on a symbol with a wide-scope expression (ie bt _<tab>), GDB can sometimes take a very long time to compile a list of symbols for completion. This large symbol list is useless anyway, nobody is going to comb through 70,000 symbols to find the right one. In these cases, we should limit the number of symbols iterated to a set limit before we bail out, and declare the symbol expression too broad for completion. This will signal to the user to enter a more tightly defined expression (which they would do, anyway), and not frustrate them with a long wait while GDB grinds through thousands of symbols to provide a completion list that is unusable. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2013-05-29 11:39 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-05-29 11:39 pmuldoon at redhat dot com [this message] 2013-05-29 15:33 ` [Bug cli/15548] " dmalcolm at redhat dot com 2013-06-03 5:16 ` dje at google dot com 2013-06-03 17:24 ` dje at google dot com 2013-06-03 19:25 ` dje at google dot com 2013-06-03 20:20 ` dje at google dot com 2013-06-25 10:08 ` manu at gcc dot gnu.org 2013-10-25 19:01 ` gbenson at redhat dot com 2013-10-25 19:09 ` dje at google dot com 2013-10-25 19:37 ` gbenson at redhat dot com 2013-11-04 13:02 ` gbenson at redhat dot com 2013-11-04 16:29 ` gbenson at redhat dot com 2014-02-12 11:40 ` gbenson at redhat dot com 2014-02-14 13:36 ` gbenson at redhat dot com 2014-02-14 13:37 ` jan.kratochvil at redhat dot com 2014-02-14 13:45 ` jan.kratochvil at redhat dot com 2014-02-14 16:13 ` gbenson at redhat dot com 2014-05-14 13:02 ` gbenson at redhat dot com 2014-09-21 8:54 ` maayan at maayank dot com 2014-09-29 11:43 ` manu at gcc dot gnu.org 2014-11-06 11:16 ` gbenson at redhat dot com 2014-11-16 20:10 ` rscrihf+sourceware at gmail dot com 2015-01-17 17:42 ` yhager at yhager dot com 2015-01-31 23:27 ` cvs-commit at gcc dot gnu.org 2015-02-02 3:32 ` cvs-commit at gcc dot gnu.org 2015-03-28 22:07 ` xdje42 at gmail dot com 2015-03-28 22:07 ` xdje42 at gmail 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=bug-15548-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).