This is the mail archive of the
gdb-testers@sourceware.org
mailing list for the GDB project.
[binutils-gdb] Don't rely on immediate_quit in command_line_input
- From: sergiodj+buildbot at sergiodj dot net
- To: gdb-testers at sourceware dot org
- Date: Tue, 12 Apr 2016 12:23:43 -0400
- Subject: [binutils-gdb] Don't rely on immediate_quit in command_line_input
- Authentication-results: sourceware.org; auth=none
*** TEST RESULTS FOR COMMIT 3212b858458dc3f2ae73e32fa066dabd56919a13 ***
Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 3212b858458dc3f2ae73e32fa066dabd56919a13
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.