From: Joel Brobecker <brobecker@adacore.com>
To: Simon Marchi <simon.marchi@ericsson.com>,
Pedro Alves <palves@redhat.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: Should this be on the blocker list for the 7.10 release?
Date: Tue, 07 Jul 2015 13:25:00 -0000 [thread overview]
Message-ID: <20150707132459.GA16734@adacore.com> (raw)
In-Reply-To: <559AE482.1010109@ericsson.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
next prev parent reply other threads:[~2015-07-07 13:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 20:26 Simon Marchi
2015-07-07 13:25 ` Joel Brobecker [this message]
2015-07-07 16:18 ` Pedro Alves
2015-07-07 18:04 ` Pedro Alves
2015-07-07 18:35 ` Simon Marchi
2015-07-07 18:47 ` Pedro Alves
2015-07-07 19:04 ` Pedro Alves
2015-07-07 19:20 ` Pedro Alves
2015-07-07 20:38 ` Simon Marchi
2015-07-07 22:04 ` Simon Marchi
2015-07-13 19:20 ` Pedro Alves
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=20150707132459.GA16734@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=simon.marchi@ericsson.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