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: Mon, 11 Jul 2011 20:53:34 +0200
- Subject: Re: [PATCH] Make interrupting tab-completion safe.
- References: <BANLkTikW2qaihdZ2zGxx6K+4q8eGzFZOr3mcbPdZsJ+2Ra=YXQ@mail.gmail.com> <20110612121158.GA10611@host1.jankratochvil.net> <BANLkTik1Z5GoCjNP9enPJeLThVk=g9Aj5ZF6zeDULburd2w=bw@mail.gmail.com> <CAEG7qUxvW4whZv2ER_x+VTpmnJ=RUQRfSb6MX3nnWE4e=UA09w@mail.gmail.com>
On Mon, 11 Jul 2011 20:42:23 +0200, Sterling Augustine wrote:
> Writing a generic reproducible test-case for this is pretty hard.
I agree about it, a testcase is possible with unchanged FSF GDB as shown in
http://sourceware.org/ml/gdb-patches/2011-06/msg00387.html
but the memory corruption is too random to rely on it in a testcase.
> Is there some other approach--short of rewriting all the *type_print*
> stuff--that would be acceptable? I'd love to close out this problem.
I find the user-facing bug as already fixed since the check-in:
http://sourceware.org/ml/gdb-patches/2011-06/msg00475.html
There are some outstanding problems being discussed (it is my turn now):
http://sourceware.org/ml/gdb-patches/2011-07/msg00233.html
but that is more for the next readline release and I hope users no longer hit
these crashes.
If you still have it reproducible with FSF GDB HEAD or 7.3 snapshots please
provide some backtrace etc.
Thanks,
Jan