async event loop and ^C
J.T. Conklin
jtc@redback.com
Fri Oct 22 12:02:00 GMT 1999
>>>>> "Elena" == Elena Zannoni <ezannoni@cygnus.com> writes:
>> My WDB backend's to_wait function polls the target for WDB events
>> (context exit, exceptions, breakpoints hit, etc.). But quit_flag is
>> checked in the polling loop. If it is set, a context suspend command
>> is sent to the target. However, with the new async event loop, ^C
>> handling is deferred until the event loop is entered so quit_flag is
>> never set.
>>
Elena> If immediate_quit is set, the handling of ^C is not deferred to the
Elena> event loop. Can you maybe set this variable?
I don't think so.
If immediate_quit is set, handle_sigint() calls async_request_quit(),
which calls quit(), which calls return_to_toplevel(). to_wait never
has a chance to send the suspend command.
--jtc
--
J.T. Conklin
RedBack Networks
More information about the Gdb
mailing list