OpenE2K
/
binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

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.
This commit is contained in:
Simon Marchi 2014-12-15 11:46:44 -05:00
parent 38bcc89d48
commit e882ef3cfc
2 changed files with 29 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gdb/testsuite/ChangeLog
View File

@ -1,3 +1,8 @@
2014-12-15 Simon Marchi <simon.marchi@ericsson.com>
* lib/gdb.exp (default_gdb_start): After starting gdb, loop
as long as we get pagination notifications.
2014-12-15 Jason Merrill <jason@redhat.com>
* Makefile.in (check-gdb.%): Restore.

11
gdb/testsuite/lib/gdb.exp
View File

@ -1451,7 +1451,7 @@ proc default_gdb_spawn { } {
# Default gdb_start procedure.
proc default_gdb_start { } {
global gdb_prompt
global gdb_prompt pagination_prompt
global gdb_spawn_id
if [info exists gdb_spawn_id] {
@ -1466,7 +1466,15 @@ proc default_gdb_start { } {
# When running over NFS, particularly if running many simultaneous
# tests on different hosts all using the same server, things can
# get really slow. Give gdb at least 3 minutes to start up.
set loop_again 1
while { $loop_again } {
set loop_again 0
gdb_expect 360 {
-re "$pagination_prompt" {
verbose "Hit pagination during startup. Pressing enter to continue."
send_gdb "\n"
set loop_again 1
}
-re "\[\r\n\]$gdb_prompt $" {
verbose "GDB initialized."
}
@ -1482,6 +1490,7 @@ proc default_gdb_start { } {
return -1
}
}
}
# force the height to "unlimited", so no pagers get used