This is the mail archive of the
mailing list for the GDB project.
Re: In async mode, use target_stop to stop the inferior
- From: Daniel Jacobowitz <drow at false dot org>
- To: Pedro Alves <pedro at codesourcery dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Fri, 14 Mar 2008 10:38:45 -0400
- Subject: Re: In async mode, use target_stop to stop the inferior
- References: <firstname.lastname@example.org>
On Fri, Mar 14, 2008 at 08:02:01AM +0000, Pedro Alves wrote:
> We do have a target method for this now. Obviouly for every
> async target other than "target (extended-)async", this wasn't
> Installed as obvious (after testing with a local gdbserver with
> the testsuite and manually).
Sorry, but I don't think this is right. Or else it deserves a better
explanation :-) async_remote_interrupt_twice didn't stop the target;
it was used to escape from a hung remote target (see interrupt_query).
You can trace the twisty path that got here through
sigint_remote_twice_token. I'm not sure what INF_QUIT_REQ should do,
or if it's necessary - I find inferior_event_handler a bit weird.