Bug ID: 25985
Summary: Control+C on python-interactive prompt crashes GDB
Assignee: unassigned at sourceware dot org
Reporter: bugmenot at mailinator dot com
Target Milestone: ---
* Start gdb
* Enter `pi` (`python-interactive`)
* Press Control+C
Expected behavior: the current line is discarded (similar to how control+C
works in other prompts)
Actual behavior: gdb crashes, without any prompt/warning. (for example, the "A
debugging session is active. Inferior 1 will be killed. Quit anyway?" prompt)
Operating system: Arch Linux
In the current version (9.1) it's possible to do nothing on Control+C (and
prevent the crash) with
--- Comment #2 from John Doe <bugmenot at mailinator dot com> ---
Edit: `signal.signal(signal.SIGINT, signal.SIG_IGN)` will make control+C do
nothing while the inferior process runs (instead of interrupting the process).
Regarding the patch: it may fix the read line reset state bug, but I think it
won't fix this bug.
You are receiving this mail because:
You are on the CC list for the bug.