]> git.ipfire.org Git - thirdparty/binutils-gdb.git/commit - gdb/testsuite/ChangeLog
[gdb/testsuite] Don't use FOOBAR pattern in gdb_test
authorTom de Vries <tdevries@suse.de>
Thu, 19 Sep 2019 17:54:15 +0000 (19:54 +0200)
committerTom de Vries <tdevries@suse.de>
Thu, 19 Sep 2019 17:54:15 +0000 (19:54 +0200)
commite452e88f54624ae55d534c4ae32e0c768cb4b59f
tree4e03a8fdd9128df26846802e823bf146ae0bc3ea
parentf64e2f4045485f99b4ce6649fdab874dacccd5a6
[gdb/testsuite] Don't use FOOBAR pattern in gdb_test

If gdb_test is used with fewer than five arguments, then the question_string
defaults to "^FOOBAR$":
...
    if [llength $args]==5 {
       set question_string [lindex $args 3]
       set response_string [lindex $args 4]
    } else {
       set question_string "^FOOBAR$"
    }
...

This can however match "FOOBAR", so perhaps "\$FOOBAR^" would have been a
better choice.

Eliminate the FOOBAR pattern from gdb_test by instead of defining a default
regexp, conditionally appending the regexp matching to a user_code variable.

Tested on x86_64-linux.

gdb/testsuite/ChangeLog:

2019-09-19  Tom de Vries  <tdevries@suse.de>

* lib/gdb.exp (gdb_test): Eliminate "^FOOBAR$" pattern.
gdb/testsuite/ChangeLog
gdb/testsuite/lib/gdb.exp