[gdb/testsuite] Fix timeout in gdb.tui/corefile-run.exp
authorTom de Vries <tdevries@suse.de>
Tue, 25 Apr 2023 06:33:57 +0000 (08:33 +0200)
committerTom de Vries <tdevries@suse.de>
Tue, 25 Apr 2023 06:33:57 +0000 (08:33 +0200)
With test-case gdb.tui/corefile-run.exp we run into:
...
WARNING: timeout in accept_gdb_output
PASS: gdb.tui/corefile-run.exp: load corefile
...

The timeout happens in this command:
...
Term::command "core-file $core"
...
because it tries to match "(gdb) $cmd" but $cmd is split over two lines:
...
   16 (gdb) core-file /data/vries/gdb/leap-15-4/build/gdb/testsuite/outputs/gdb.tui/co
   17 refile-run/corefile-run.core
   18 [New LWP 5370]
   19 Core was generated by `/data/vries/gdb/leap-15-4/build/gdb/testsuite/outputs/gdb
   20 .tui/corefile-run/coref'.
   21 Program terminated with signal SIGTRAP, Trace/breakpoint trap.
   22 #0  main () at tui-layout.c:21
   23 (gdb)
...

Fix this by using send_gdb "$cmd\n" and wait_for "Program terminated" instead.

Tested on x86_64-linux.

gdb/testsuite/gdb.tui/corefile-run.exp

index 6769dfbd80005456fcfa3e7caa1661307a4cdb8a..a81d7e7c208cb1c529b55c3f75301f5837abe32d 100644 (file)
@@ -63,7 +63,8 @@ set text [Term::get_all_lines]
 gdb_assert {![string match "No Source Available" $text]} \
     "initial source listing"
 
-Term::command "core-file $core"
+send_gdb "core-file $core\n"
+Term::wait_for "Program terminated"
 Term::check_contents "load corefile" "$src_line_nr *$src_line.*$gdb_prompt .*"
 
 Term::command "run"