public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug cli/15548] Limit completions to a pre-defined limit when completions list is very large Date: Mon, 29 Sep 2014 11:43:00 -0000 [thread overview] Message-ID: <bug-15548-4717-ANH9uaE99d@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-15548-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=15548 --- Comment #13 from Manuel López-Ibáñez <manu at gcc dot gnu.org> --- (In reply to Gary Benson from comment #9) > After having implemented this > (https://sourceware.org/ml/gdb-patches/2014-02/msg00398.html) I'm coming to > the conclusion that you can't rememdy this problem this way. At least you can alleviate it! > This list only has 875 candidates, but GDB still has to expand pretty much > every symbol table to root them all out. A limit of 1000 here will not stop > the user seeing a lengthy pause. The two issues seem to be important to fix. And the issue here already has a patch that is basically approved! The problem is not only a lengthy pause (which is annoying but it is a different issue), it is also that after the pause, Emacs may spend a several *minutes* printing candidates, slowing the whole computer down with it. A limit of 1000 seems almost too much, 150 or so seems much more manageable. Please, can you commit your patch so at least there is some progress on this? -- You are receiving this mail because: You are on the CC list for the bug. >From gdb-prs-return-16752-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Sep 29 19:35:54 2014 Return-Path: <gdb-prs-return-16752-listarch-gdb-prs=sources.redhat.com@sourceware.org> Delivered-To: listarch-gdb-prs@sources.redhat.com Received: (qmail 28481 invoked by alias); 29 Sep 2014 19:35:53 -0000 Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: <gdb-prs.sourceware.org> List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org> List-Archive: <http://sourceware.org/ml/gdb-prs/> List-Post: <mailto:gdb-prs@sourceware.org> List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs> Sender: gdb-prs-owner@sourceware.org Delivered-To: mailing list gdb-prs@sourceware.org Received: (qmail 28449 invoked by uid 48); 29 Sep 2014 19:35:52 -0000 From: "jim.kearney at oracle dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug backtrace/16215] SPARC: can't compute CFA for this frame Date: Mon, 29 Sep 2014 19:35:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: backtrace X-Bugzilla-Version: 7.6 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jim.kearney at oracle dot com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: <bug-16215-4717-Q8Lr3g1v7M@http.sourceware.org/bugzilla/> In-Reply-To: <bug-16215-4717@http.sourceware.org/bugzilla/> References: <bug-16215-4717@http.sourceware.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-q3/txt/msg00741.txt.bz2 Content-length: 399 https://sourceware.org/bugzilla/show_bug.cgi?id\x16215 Jim Kearney <jim.kearney at oracle dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jim.kearney at oracle dot com -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-09-29 11:43 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-05-29 11:39 [Bug cli/15548] New: " pmuldoon at redhat dot com 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 [this message] 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-ANH9uaE99d@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).