Re: Inadvertently run inferior threads
Eli Zaretskii <[email protected]>
| Newsgroups | gmane.comp.gdb.devel |
|---|---|
| Message-ID | <[email protected]> |
> Date: Mon, 15 Jun 2015 14:07:57 +0100 > From: Pedro Alves <[email protected]> > CC: [email protected] > > > 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?