From: Paul Koning <paul_koning@dell.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: "Tom Tromey" <tromey@redhat.com>,
"Kristoffer Sjöö" <krsj@nada.kth.se>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Hangs in GDB auto-complete
Date: Tue, 16 Nov 2010 18:00:00 -0000 [thread overview]
Message-ID: <92A8CBDB-2FAB-4A67-905B-4EA8F20B904D@dell.com> (raw)
In-Reply-To: <4CE2C45F.9010502@vmware.com>
On Nov 16, 2010, at 12:50 PM, Michael Snyder wrote:
> Tom Tromey wrote:
>>>>>>> "Kristoffer" == Kristoffer Sjöö <krsj@nada.kth.se> 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 ...
>
Yes, that's something I run into every week or two, when I hit tab in the wrong spot.
paul
next prev parent reply other threads:[~2010-11-16 18:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 12:31 Kristoffer Sjöö
2010-11-16 17:21 ` Tom Tromey
2010-11-16 17:50 ` Michael Snyder
2010-11-16 18:00 ` Paul Koning [this message]
2010-11-17 10:35 ` Kristoffer Sjöö
2010-11-18 21:31 ` Tom Tromey
2010-11-23 13:43 ` Kristoffer Sjöö
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=92A8CBDB-2FAB-4A67-905B-4EA8F20B904D@dell.com \
--to=paul_koning@dell.com \
--cc=gdb@sourceware.org \
--cc=krsj@nada.kth.se \
--cc=msnyder@vmware.com \
--cc=tromey@redhat.com \
/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: link
Be 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