diff options
author | Simon Marchi <simon.marchi@ericsson.com> | 2017-02-10 16:29:50 -0500 |
---|---|---|
committer | Simon Marchi <simon.marchi@ericsson.com> | 2017-02-10 16:29:50 -0500 |
commit | 26a06916b684ceda25c2edb43141e1101bf337c6 (patch) | |
tree | c88cd8c63f2fb008e8962f98fea4fb0643e085d8 /gdb/testsuite | |
parent | b761ca9e3d6e9c0f1762e0994dfdf2b989e3fc21 (diff) | |
download | gdb-26a06916b684ceda25c2edb43141e1101bf337c6.zip gdb-26a06916b684ceda25c2edb43141e1101bf337c6.tar.gz gdb-26a06916b684ceda25c2edb43141e1101bf337c6.tar.bz2 |
Do not send queries on secondary UIs
This is a follow-up to
https://sourceware.org/ml/gdb-patches/2017-02/msg00261.html
This patch restricts queries to the main UI, which allows to avoid two
different problems.
The first one is that GDB is issuing queries on secondary MI channels
for which a TTY is allocated. The second one is that GDB is not able to
handle queries on two (CLI) UIs simultaneously. Restricting queries to
the main UI allows to bypass these two problems.
More details on how/why these two problems happen:
1. Queries on secondary MI UI
The current criterion to decide if we should query the user is whether
the input stream is a TTY. The original way to start GDB in MI mode
from a front-end was to create a subprocess with pipes to its
stdin/stdout. In this case, the input was considered non-interactive
and queries were auto-answered. Now that front-ends can create the MI
channel as a separate UI connected to a dedicated TTY, GDB now
considers this input stream as interactive and sends queries to it.
By restricting queries to the main UI, we make sure we never query on
the secondary MI UI.
2. Simultaneous queries
As Pedro stated it, when you have two queries on two different CLI UIs
at the same time, you end up with the following pseudo stack:
#0 gdb_readline_wrapper
#1 defaulted_query // for UI #2
#2 handle_command
#3 execute_command ("handle SIGTRAP" ....
#4 stdin_event_handler // input on UI #2
#5 gdb_do_one_event
#7 gdb_readline_wrapper
#8 defaulted_query // for UI #1
#9 handle_command
#10 execute_command ("handle SIGINT" ....
#11 stdin_event_handler // input on UI #1
#12 gdb_do_one_event
#13 gdb_readline_wrapper
trying to answer the query on UI #1 will therefore answer for UI #2.
By restricting the queries to the main UI, we ensure that there will
never be more than one pending query, since you can't have two queries
on a UI at the same time.
I added a snippet to gdb.base/new-ui.exp to verify that we get a query
on the main UI, but that we don't on the secondary one (or, more
precisely, that it gets auto-answered).
gdb/ChangeLog:
* utils.c (defaulted_query): Don't query on secondary UIs.
gdb/testsuite/ChangeLog:
* gdb.base/new-ui.exp (do_test): Test queries behavior on main
and extra UIs.
Diffstat (limited to 'gdb/testsuite')
-rw-r--r-- | gdb/testsuite/ChangeLog | 5 | ||||
-rw-r--r-- | gdb/testsuite/gdb.base/new-ui.exp | 12 |
2 files changed, 17 insertions, 0 deletions
diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog index 3274b40..c1e53b7 100644 --- a/gdb/testsuite/ChangeLog +++ b/gdb/testsuite/ChangeLog @@ -1,5 +1,10 @@ 2017-02-10 Simon Marchi <simon.marchi@ericsson.com> + * gdb.base/new-ui.exp (do_test): Test queries behavior on main + and extra UIs. + +2017-02-10 Simon Marchi <simon.marchi@ericsson.com> + * gdb.base/new-ui.exp (do_test, do_test_invalid_args): Use proc_with_prefix. diff --git a/gdb/testsuite/gdb.base/new-ui.exp b/gdb/testsuite/gdb.base/new-ui.exp index 8224b7d..b84f4de 100644 --- a/gdb/testsuite/gdb.base/new-ui.exp +++ b/gdb/testsuite/gdb.base/new-ui.exp @@ -128,6 +128,18 @@ proc_with_prefix do_test {} { gdb_test "print 2" "^print 2\r\n\\\$2 = 2" "print on extra console" } + # Verify that we get proper queries on the main UI, but that they are + # auto-answered on secondary UIs. + with_spawn_id $gdb_main_spawn_id { + gdb_test "delete" "" "delete all breakpoint on main console" \ + "Delete all breakpoints. .y or n. $" "n" + } + with_spawn_id $extra_spawn_id { + gdb_test "delete" \ + "Delete all breakpoints. .y or n. .answered Y; input not from terminal." \ + "delete all breakpoints on extra console" + } + # Run a few execution tests with the main console as the driver # console. with_test_prefix "main console" { |