From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7943 invoked by alias); 14 Feb 2014 13:36:57 -0000 Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-prs-owner@sourceware.org Received: (qmail 7908 invoked by uid 48); 14 Feb 2014 13:36:56 -0000 From: "gbenson at redhat dot com" 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:36:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: gbenson at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: gbenson at redhat dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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-q1/txt/msg00188.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=15548 --- Comment #9 from Gary Benson --- 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. Here's an example where it can work: $ gdb /usr/lib64/libreoffice/program/soffice.bin (gdb) start (gdb) b GDB tries to expand every symbol table. With a limit of 1000 completions, GDB quickly hits the limit and returns control to the user. Here's an example of where this method fails: $ gdb /usr/lib64/libreoffice/program/soffice.bin (gdb) start (gdb) b m 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. I propose to continue discussing this issue as bug 11920, which refers to the problem (namely that tab completion might stall the CLI without feedback) rather than to this specific solution. I will close this bug as RESOLVED INVALID in one week if nobody objects. -- You are receiving this mail because: You are on the CC list for the bug.