This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Make interrupting tab-completion safe.
- From: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- To: Sterling Augustine <saugustine at google dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Sun, 12 Jun 2011 14:11:58 +0200
- Subject: Re: [PATCH] Make interrupting tab-completion safe.
- References: <BANLkTikW2qaihdZ2zGxx6K+4q8eGzFZOr3mcbPdZsJ+2Ra=YXQ@mail.gmail.com>
On Sat, 11 Jun 2011 02:19:05 +0200, Sterling Augustine wrote:
> gdb <really big program>
> b <tab><tab>
> [ctrl-c before tab-completion is done]
> b <tab>
> (segmentation fault)
I do not have it reproducuble, does not happen for you for ./gdb -nx ./gdb?
Tried also Firefox, both processing runs long enough to CTRL-C it.
It would be good to have a testcase for regressions anyway.
> The problem comes because the dwarf2read.c tries to discover the full
> linkage name of symbols, and assumes that it won't be interrupted.
I had rather an idea to make it interruption-safe as this way another
forgotten or newly introduced QUIT may regression it. But I do not have
a reproducer to check where the crash happens.
Thanks,
Jan