Don't call clear_quit_flag in command_handler
authorPedro Alves <palves@redhat.com>
Tue, 12 Apr 2016 15:49:30 +0000 (16:49 +0100)
committerPedro Alves <palves@redhat.com>
Tue, 12 Apr 2016 15:55:16 +0000 (16:55 +0100)
commit4a81fd47b3052f4c1601f8eb7f7879b12e0473cd
tree814985bc78456d798faf70e518e4501431ebfce1
parentabf009ef94d2f89b09767cce30bcf99224c1a0a9
Don't call clear_quit_flag in command_handler

This just looks totally wrong to me, for completetly discarding a
user-requested Ctrl-C.  I can't think of why we'd want do this here.

Actually, I digged the history, and found out that this has been here
since at least 7b4ac7e1ed2c (gdb-2.4, the initial revision, 1988), at
a time were we had a top level setjmp/longjmp, long before that got
wrapped in throw_exception and friends, and this code was in an
explicit loop, with the quit_flag cleared on every iteration, before
executing a command...

gdb/ChangeLog:
2016-04-12  Pedro Alves  <palves@redhat.com>

* event-top.c (command_handler): Don't call clear_quit_flag.
gdb/ChangeLog
gdb/event-top.c