From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31133 invoked by alias); 16 Nov 2010 17:50:36 -0000 Received: (qmail 31125 invoked by uid 22791); 16 Nov 2010 17:50:35 -0000 X-SWARE-Spam-Status: No, hits=-4.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from smtp-outbound-2.vmware.com (HELO smtp-outbound-2.vmware.com) (65.115.85.73) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 16 Nov 2010 17:50:27 +0000 Received: from mailhost4.vmware.com (mailhost4.vmware.com [10.16.67.124]) by smtp-outbound-2.vmware.com (Postfix) with ESMTP id 0B2021B001; Tue, 16 Nov 2010 09:50:24 -0800 (PST) Received: from msnyder-server.eng.vmware.com (promd-2s-dhcp138.eng.vmware.com [10.20.124.138]) by mailhost4.vmware.com (Postfix) with ESMTP id F16CBC9A5F; Tue, 16 Nov 2010 09:50:23 -0800 (PST) Message-ID: <4CE2C45F.9010502@vmware.com> Date: Tue, 16 Nov 2010 17:50:00 -0000 From: Michael Snyder User-Agent: Thunderbird 2.0.0.24 (X11/20101027) MIME-Version: 1.0 To: Tom Tromey CC: =?UTF-8?B?S3Jpc3RvZmZlciBTasO2w7Y=?= , "gdb@sourceware.org" Subject: Re: Hangs in GDB auto-complete References: <4CE279B5.5010501@nada.kth.se> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2010-11/txt/msg00070.txt.bz2 Tom Tromey wrote: >>>>>> "Kristoffer" == Kristoffer Sjöö writes: > > Kristoffer> After I upgraded my Ubuntu system to Lucid Lynx (10.04) > > What version of gdb? > > Kristoffer> It's very irritating, especially when I end up having to > Kristoffer> kill GDB. > > You should be able to C-c out of any completion. > If you can't, then that is a gdb bug. > > Kristoffer> I've no notion of the inner workings of GDB and no idea what > Kristoffer> this is all due to, but perhaps someone here has some clue? > > We need more details, ideally enough to try to reproduce the problem. > It could be any number of things, depending on the details of what you > are doing. I think I've seen something like this -- on large symbol files with many symbols, gdb gets into a tight loop in completion that doesn't seem to respond to ^C. Just speaking from memory ...