This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Should this be on the blocker list for the 7.10 release?
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Simon Marchi <simon dot marchi at ericsson dot com>, Pedro Alves <palves at redhat dot com>
- Cc: gdb-patches <gdb-patches at sourceware dot org>
- Date: Tue, 7 Jul 2015 06:24:59 -0700
- Subject: Re: Should this be on the blocker list for the 7.10 release?
- Authentication-results: sourceware.org; auth=none
- References: <559AE482 dot 1010109 at ericsson dot com>
> I filed this bug recently:
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=18600
>
> In short, gdb sometimes leaves stopped newly spawned threads created by a
> fork child. The "sometimes" happens quite often, so it's very easy to
> reproduce. This has the effect of leaving (part) of your program stopped
> while you expect it to be running. "info threads" shows the threads as
> running while in reality they aren't.
>
> Is this bug serious enough to be on the blocking list for 7.10? I would
> think so, as it's a regression compared to 7.9. However, I don't want
> to impose work on anybody (e.g. Pedro, or anybody else familiar with the
> linux-nat subsystem), which is why I am asking. I am willing to put time
> on this, but the chances of me successfully fixing the bug are quite slim.
Not sure. I think Pedro would be in a better position to answer.
For now, I've put this issue as a "maybe" for 7.10; so we will not
release until this is fixed, or we explicitly decide it's OK for 7.10.
Pedro?
--
Joel