This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Inadvertently run inferior threads
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Pedro Alves <palves at redhat dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Mon, 15 Jun 2015 19:37:18 +0300
- Subject: Re: Inadvertently run inferior threads
- Authentication-results: sourceware.org; auth=none
- References: <83h9tq3zu3 dot fsf at gnu dot org> <55043A63 dot 6020103 at redhat dot com> <8361a339xd dot fsf at gnu dot org> <5504555C dot 804 at redhat dot com> <550458E0 dot 10206 at redhat dot com> <83y4jrsgui dot fsf at gnu dot org> <83k2vas7f1 dot fsf at gnu dot org> <83zj43q3et dot fsf at gnu dot org> <557ECBE5 dot 4040108 at redhat dot com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Mon, 15 Jun 2015 13:58:13 +0100
> From: Pedro Alves <palves@redhat.com>
> CC: gdb-patches@sourceware.org
>
> On 06/13/2015 12:00 PM, Eli Zaretskii wrote:
> > Ping! With the GDB 7.10 branching date looming, could we please
> > decide ASAP if the patch I proposed for this annoying problem is good
> > to go in?
>
> Off hand, I don't think the patch is correct. I'll need a bit more
> to think this through and give a better response. I'm not seeing why
> target_can_async targets would be special here: target_can_async targets
> also stop all threads when they report an event out of target_wait.
One difference is that in the former case, the call to set_running
marks _all_ the threads running.
But I'm okay with making this a MinGW-specific change, since other
platforms need to do something extraordinary to get into this
situation, while on Windows this happens out of my or the inferior's
control, and its effect on the debugging session is so devastating.
> Meanwhile, the way to make sure that we don't forget
> considering fixing something for the release, is to list it
> in the wiki's release page:
>
> https://sourceware.org/gdb/wiki/GDB_7.10_Release
Done. I hope I formatted the entry according to expectations.