This is the mail archive of the
gdb@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 at sourceware dot org
- Date: Mon, 15 Jun 2015 18:15:23 +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> <83616vtx40 dot fsf at gnu dot org> <557ECE2D dot 1000707 at redhat dot com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Mon, 15 Jun 2015 14:07:57 +0100
> From: Pedro Alves <palves@redhat.com>
> CC: gdb@sourceware.org
>
> > It seems like 'interrupt' does nothing in native debugging of a target
> > that doesn't support async execution, at least on MS-Windows. Is that
> > a bug, or is it expected?
>
> It's old code, but I think the idea of the target_can_async check
> in interrupt_command is "this shouldn't even be possible". If the
> target doesn't support async execution, you're not supposed to
> be able to end up with a prompt while the target is running
> in the first place.
IOW, we don't have even a fire escape when something like that
happens. Would it be a good idea to have at least a maint command to
stop a thread, or all threads?