[Bug remote/18772] gdb does not respond to CTRL-C

["filip.bascarevic at siemens dot com" <sourceware-bugzilla@sourceware.org>]

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

Filip Bascarevic <filip.bascarevic at siemens dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |filip.bascarevic at siemens dot co
                   |                            |m

--- Comment #15 from Filip Bascarevic <filip.bascarevic at siemens dot com> ---
(In reply to Pedro Alves from comment #13)
> Once I'm done with my current priorities, my next project will be going back
> to this:
> 
>  [PATCH v2 00/16] Interrupting programs that block/ignore SIGINT
>  https://pi.simark.ca/gdb-patches/20210614212410.1612666-1-pedro@palves.net/
> 
> That redesigns how SIGINT is handled when native debugging, such that GDB
> _always_ gets the SIGINT first instead of relying on the inferior getting
> it, so I suspect it will fix Andrew's testcase when native debugging (though
> I haven't tried it).  As for remote debugging with gdbserver, I will take a
> look at it too, once I resume work on that series.

Hello community,

it seems this patch also broke Eclipse Suspend functionality during debugging.
I think the Eclipse also sends CTRL-C when the user presses Suspend button. I
noticed it from the GDB release 11.1 (10.2 works). 
Used remote debugging of the Qemu target Aarch64 with Eclipse in Windows. 
Feel free to contact me for any support or additional information

Best regards, 
Filip Bascarevic

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