Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Sterling Augustine <saugustine@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Make interrupting tab-completion safe.
Date: Mon, 11 Jul 2011 18:54:00 -0000	[thread overview]
Message-ID: <20110711185334.GA10138@host1.jankratochvil.net> (raw)
In-Reply-To: <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


  reply	other threads:[~2011-07-11 18:53 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-11  0:19 Sterling Augustine
2011-06-12 12:12 ` Jan Kratochvil
2011-06-13 17:45   ` Sterling Augustine
2011-06-26 22:22     ` [readline patch, gdb-7.3?] Avoid free from a signal handler [Re: [PATCH] Make interrupting tab-completion safe.] Jan Kratochvil
2011-06-27 16:03       ` Joel Brobecker
2011-06-29 21:49         ` Jan Kratochvil
2011-06-29 13:54       ` [Bug-readline] " Chet Ramey
2011-06-29 20:35         ` Jan Kratochvil
2011-06-30 14:38           ` Chet Ramey
2011-07-06 16:03             ` Jan Kratochvil
2011-07-06 16:07               ` Chet Ramey
2011-07-06 17:42                 ` Jan Kratochvil
2011-07-07 13:40                   ` Chet Ramey
2011-07-08 16:03                     ` Chet Ramey
2011-10-19 20:30                       ` Jan Kratochvil
2011-10-19 17:02                     ` Jan Kratochvil
2011-10-19 17:51                       ` Pedro Alves
2011-10-19 18:50                       ` Chet Ramey
2011-07-11 18:53     ` [PATCH] Make interrupting tab-completion safe Sterling Augustine
2011-07-11 18:54       ` Jan Kratochvil [this message]
     [not found]         ` <CAEG7qUxFvEoJ-E2YsoFPL-tKoK4kD3-pKn-h31uUeXQoDD2Gaw@mail.gmail.com>
2011-07-12 15:59           ` [dwarf2_mark_helper patch] " Jan Kratochvil
2011-07-12 17:48             ` Sterling Augustine
2011-07-12 18:56             ` Jan Kratochvil
2011-07-12 21:18             ` [commit] " Jan Kratochvil
2011-07-12 21:42               ` Tom Tromey
2011-07-12 22:51                 ` Jan Kratochvil

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=20110711185334.GA10138@host1.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=saugustine@google.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