]> git.ipfire.org Git - thirdparty/binutils-gdb.git/commit - gdb/testsuite/ChangeLog
[gdb/testsuite] Fix gdb.dwarf2/frame-inlined-in-outer-frame.exp
authorTom de Vries <tdevries@suse.de>
Tue, 8 Sep 2020 09:51:29 +0000 (11:51 +0200)
committerTom de Vries <tdevries@suse.de>
Tue, 8 Sep 2020 09:51:29 +0000 (11:51 +0200)
commitcac1e71dbd365fd59c916600b654b0920a7475cd
tree74039f5bc1caa05f93f1f452efa640dff8b34810
parentb5ffa9182b5cfa038c494e4199224a90955d635d
[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.
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.dwarf2/frame-inlined-in-outer-frame.exp