https://bugs.kde.org/show_bug.cgi?id=411789
Bug ID: 411789
Summary: When debugging in GDB, doing Run | Interrupt does not
send SIGINT to GDB.
Product: kdevelop
Version: 5.3.2
Platform: MS Windows
OS: MS Windows
Status: REPORTED
Severity: normal
Priority: NOR
Component: CPP Debugger
Assignee: kdevelop-bugs-n...@kde.org
Reporter: kdeb...@funkster.org
CC: niko.s...@gmail.com
Target Milestone: ---
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.
--
You are receiving this mail because:
You are watching all bug changes.
