[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  <tdevries@suse.de>

	* gdb.dwarf2/frame-inlined-in-outer-frame.exp: Consume gdb prompt
	after gdb_starti_cmd.
This commit is contained in:
Tom de Vries
2020-09-08 11:51:29 +02:00
parent b5ffa9182b
commit cac1e71dbd
2 changed files with 6 additions and 0 deletions

View File

@ -1,3 +1,8 @@
2020-09-08 Tom de Vries <tdevries@suse.de>
* gdb.dwarf2/frame-inlined-in-outer-frame.exp: Consume gdb prompt
after gdb_starti_cmd.
2020-09-03 Alok Kumar Sharma <AlokKumar.Sharma@amd.com> 2020-09-03 Alok Kumar Sharma <AlokKumar.Sharma@amd.com>
* lib/fortran.exp (fortran_complex8): New proc. * lib/fortran.exp (fortran_complex8): New proc.

View File

@ -105,6 +105,7 @@ if { [gdb_starti_cmd] != 0 } {
fail "failed to run to first instruction" fail "failed to run to first instruction"
return return
} }
gdb_test "" "Program stopped.*" "starti prompt"
gdb_test "frame" "in _start .*" gdb_test "frame" "in _start .*"