[Bug remote/15297] CTRL-C with set debug remote often crashes GDB

["pedro at palves dot net" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=15297

Pedro Alves <pedro at palves dot net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |14.1
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #7 from Pedro Alves <pedro at palves dot net> ---
> However, running Jan's test, on current master reveals we still have problems 
> with a Ctrl-c coming in while Python code is running:
> ...
>
> That "^CPython Exception <class 'KeyboardInterrupt'> <class 
> 'KeyboardInterrupt'>: " is probably from the Python frame unwinder machinery.
> At that point the target has the terminal, and since 
> 2f99e8fc9cb84ca80cfca6c119f1f22bbfd2a314 this should not have happened (Change 
> SIGINT handler for extension languages only when target terminal is ours), but 
> something's still not right over there.  I suspect that it's because now 
> remote.c uses the standard SIGINT handler, which calls set_quit_flag, which 
> calls active_ext_lang->ops->set_quit_flag.

So I think this issue is finally fixed by this series:

https://inbox.sourceware.org/gdb-patches/20230210233604.2228450-1-pedro@palves.net/T/#m79098ae4ed85a49c9693a47a0ad7a139f63d47dd

There's a separate PR about Ctrl-C and Python unwinder during execution:

  https://sourceware.org/bugzilla/show_bug.cgi?id=26266

which is really the same thing, and I'm leaving that open, hoping for a
testcase.  So we can close this one.

-- 
You are receiving this mail because:
You are on the CC list for the bug.