Don't rely on immediate_quit in command_line_input
authorPedro Alves <palves@redhat.com>
Tue, 12 Apr 2016 15:49:29 +0000 (16:49 +0100)
committerPedro Alves <palves@redhat.com>
Tue, 12 Apr 2016 15:49:29 +0000 (16:49 +0100)
commit3212b858458dc3f2ae73e32fa066dabd56919a13
treeab29e8bf9b3e8fee57e4ab1f37ae8eafc0975da6
parentf36e33dac1a97cca8f79ca8b20cf0fb05f1e25f4
Don't rely on immediate_quit in command_line_input

AFAICS, immediate_quit was only needed here nowdays to be able to
interrupt gdb_readline_no_editing.

command_line_input can also take the gdb_readline_wrapper path, but
since that is built on top of the event loop (gdb_select / poll and
asynchronous signal handlers), it can be interrupted.

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

* top.c: Include "gdb_select.h".
(gdb_readline_no_editing): Wait for input with gdb_select instead
of blocking in fgetc.
(command_line_input): Don't set immediate_quit.
gdb/ChangeLog
gdb/top.c
This page took 0.02665 seconds and 4 git commands to generate.