diff options
author | Simon Marchi <simon.marchi@ericsson.com> | 2014-12-15 11:46:44 -0500 |
---|---|---|
committer | Simon Marchi <simon.marchi@ericsson.com> | 2014-12-15 11:46:44 -0500 |
commit | e882ef3cfc3d991433c3b9aed104961ad3ce5904 (patch) | |
tree | 022d5225927a7706fa7c209ddfd3f7fb8a97e6ae /gdb/target.c | |
parent | 38bcc89d48a20af944fe0d51eff3980f7dc8a88e (diff) | |
download | gdb-e882ef3cfc3d991433c3b9aed104961ad3ce5904.zip gdb-e882ef3cfc3d991433c3b9aed104961ad3ce5904.tar.gz gdb-e882ef3cfc3d991433c3b9aed104961ad3ce5904.tar.bz2 |
testsuite: expect possible pagination when starting gdb
When gdb starts, the lines that appear before the first prompt may get
paginated if the terminal in which the tests are ran is too small (in
terms of rows). These lines include the welcome/license message and
possibly more, such as "Reading symbols from...". Pagination is disabled
right after gdb is started (with "set height 0"), but this output happens
before we are able to set height.
If these lines get paginated, gdb waits for the user to press enter and
the test harness waits for gdb to print its prompt, resulting in a
deadlock.
My first idea was to launch gdb with --quiet. However, some lines are
still printed ("Reading symbols from...", some more stuff when attaching
with --pid, etc).
The proposed solution simply expects that pagination can occur after
starting gdb. If this is the case, it sends a "\n" and loops.
gdb/testsuite/Changelog:
* lib/gdb.exp (default_gdb_start): After starting gdb, loop
as long as we get pagination notifications.
Diffstat (limited to 'gdb/target.c')
0 files changed, 0 insertions, 0 deletions