Fix stdin ending up not registered after a Quit
authorPedro Alves <palves@redhat.com>
Thu, 16 Nov 2017 18:44:43 +0000 (18:44 +0000)
committerPedro Alves <palves@redhat.com>
Thu, 16 Nov 2017 18:44:43 +0000 (18:44 +0000)
commit38dc2859c464733314c591d30a5359db20167f7f
tree0c518e1479683146115913a61c381b4fe6946dfb
parent688fca4fe6c83a6802731faa8455d177998d614d
Fix stdin ending up not registered after a Quit

If you press Ctrl-C while GDB is processing breakpoint commands the
TRY/CATCH in inferior_event_handler catches the Quit exception and
prints it, and then if the interpreter was running a foreground
execution command, nothing re-adds stdin back in the event loop,
meaning the debug session ends up busted, because the user can't type
anything...

This was exposed by the new gdb.base/bp-cmds-continue-ctrl-c.exp
testcase added later in the series.

gdb/ChangeLog:
2017-11-16  Pedro Alves  <palves@redhat.com>

* inf-loop.c (inferior_event_handler): Don't swallow the exception
if the prompt is blocked.
gdb/ChangeLog
gdb/inf-loop.c