Bug 411789

Summary: When debugging in GDB, doing Run | Interrupt does not send SIGINT to GDB.
Product: [Applications] kdevelop Reporter: Funkster <kdebugs>
Component: CPP DebuggerAssignee: kdevelop-bugs-null
Status: REPORTED ---    
Severity: normal CC: niko.sams
Priority: NOR    
Version First Reported In: 5.3.2   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Funkster 2019-09-10 11:29:24 UTC
SUMMARY
When debugging and the program is running, doing Run | Interrupt (or clicking the pause button in the GDB panel) does not send SIGINT to GDB and thus execution is not paused.

STEPS TO REPRODUCE
1. Debug a program that runs forever (e.g. while (1)) in GDB
2. Run | Interrupt

OBSERVED RESULT
Nothing happens.

EXPECTED RESULT
Execution is stopped, frame stack indicates current execution position.

SOFTWARE/OS VERSIONS
Windows: 10

ADDITIONAL INFORMATION
I made sure that the GDB I'm using does respond to SIGINT by running a manual debug session and sending SIGINT using kill -SIGINT <pid> from another console (MinGW bash shell).

I've got a feeling this works under Linux.