From cac1e71dbd365fd59c916600b654b0920a7475cd Mon Sep 17 00:00:00 2001 From: Tom de Vries Date: Tue, 8 Sep 2020 11:51:29 +0200 Subject: [PATCH] [gdb/testsuite] Fix gdb.dwarf2/frame-inlined-in-outer-frame.exp I'm running into the following FAIL: ... (gdb) starti ^M Starting program: frame-inlined-in-outer-frame frame^M ^M ^M Program stopped.^M 0x0000000000401000 in _start ()^M (gdb) PASS: gdb.dwarf2/frame-inlined-in-outer-frame.exp: frame frame^M (gdb) FAIL: gdb.dwarf2/frame-inlined-in-outer-frame.exp: step into foo stepi^M 0x0000000000401001 in foo ()^M ... The problem is that the .exp file issues a gdb_starti_cmd without consuming the resulting prompt. Consequently, the gdb_test issuing the frame command consumes that prompt, and things are out-of-sync from that point onwards. Fix this by consuming the gdb prompt after gdb_starti_cmd. Tested on x86_64-linux. gdb/testsuite/ChangeLog: 2020-09-08 Tom de Vries * gdb.dwarf2/frame-inlined-in-outer-frame.exp: Consume gdb prompt after gdb_starti_cmd. --- gdb/testsuite/ChangeLog | 5 +++++ gdb/testsuite/gdb.dwarf2/frame-inlined-in-outer-frame.exp | 1 + 2 files changed, 6 insertions(+) diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog index 854dca5128e..33987e469a6 100644 --- a/gdb/testsuite/ChangeLog +++ b/gdb/testsuite/ChangeLog @@ -1,3 +1,8 @@ +2020-09-08 Tom de Vries + + * gdb.dwarf2/frame-inlined-in-outer-frame.exp: Consume gdb prompt + after gdb_starti_cmd. + 2020-09-03 Alok Kumar Sharma * lib/fortran.exp (fortran_complex8): New proc. diff --git a/gdb/testsuite/gdb.dwarf2/frame-inlined-in-outer-frame.exp b/gdb/testsuite/gdb.dwarf2/frame-inlined-in-outer-frame.exp index 721b521e830..0ded2c0e766 100644 --- a/gdb/testsuite/gdb.dwarf2/frame-inlined-in-outer-frame.exp +++ b/gdb/testsuite/gdb.dwarf2/frame-inlined-in-outer-frame.exp @@ -105,6 +105,7 @@ if { [gdb_starti_cmd] != 0 } { fail "failed to run to first instruction" return } +gdb_test "" "Program stopped.*" "starti prompt" gdb_test "frame" "in _start .*" -- 2.30.2