public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <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: Fri, 14 Feb 2014 13:45:00 -0000 [thread overview] Message-ID: <bug-15548-4717-OshLUDQIhj@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 #10 from Jan Kratochvil <jan.kratochvil at redhat dot com> --- I think you are hitting here the problem of Fedora debuginfo dwz PR 16405 which I (or anyone) has not fixed yet. On dwz debuginfo GDB has problem to resolve just several symbols (in a backtrace) because it (needlessly) expands tons of dwz-included CUs. You should try it on debuginfo without dwz (such as RHEL-6 etc.). -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-02-14 13:45 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 [this message] 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-OshLUDQIhj@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).