]> git.ipfire.org Git - thirdparty/binutils-gdb.git/commit - gdb/testsuite/ChangeLog
gdb/testsuite: use gdb_test_no_output instead of send_gdb
authorAndrew Burgess <andrew.burgess@embecosm.com>
Fri, 7 May 2021 21:14:27 +0000 (22:14 +0100)
committerAndrew Burgess <andrew.burgess@embecosm.com>
Fri, 7 May 2021 21:19:41 +0000 (22:19 +0100)
commita3237c7cc7de4b3ea44d8874a0c90dff1f4d31dc
tree6086d7008406c4b0f009fca6d5f4a45f476d7d23
parent91e3c425d6adb4797a2137dd9126a2f19e1833d8
gdb/testsuite: use gdb_test_no_output instead of send_gdb

I noticed gdb.base/ptype-offsets.exp failing occasionally, this was
due to lines like this in the test script:

  send_gdb "set print type hex on\n"

As this does not match the '(gdb)' prompt that is produced, the prompt
would sometimes be matched against the next test, causing the next
test to think its output was missing and fail.

Fix this by switching to:

  gdb_test_no_output "set print type hex on"

gdb/testsuite/ChangeLog:

* gdb.base/ptype-offsets.exp: Replace use of send_gdb with
gdb_test_no_output.
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.base/ptype-offsets.exp