Fix spurious FAILs with examine-backward.exp
authorAndreas Arnez <arnez@linux.vnet.ibm.com>
Mon, 20 Mar 2017 17:55:39 +0000 (18:55 +0100)
committerAndreas Arnez <arnez@linux.vnet.ibm.com>
Mon, 20 Mar 2017 17:55:39 +0000 (18:55 +0100)
commit59a561480d547d041127630b1ba17a284eef8225
tree285bbe79b89dc9bc5dcdeee7592e6b7f1afe720c
parent39e224f6f9ee3f6123d4c9ddb7c0955e0604c1b4
Fix spurious FAILs with examine-backward.exp

The test case examine-backward.exp issues the command "x/-s" after the end
of the first string in TestStrings, but without making sure that this
string is preceded by a string terminator.  Thus GDB may spuriously print
some random characters from before that string, and then the test fails.

This patch assures that TestStrings is preceded by a string terminator.

gdb/testsuite/ChangeLog:

* gdb.base/examine-backward.c (Barrier): New character array
constant, to ensure that TestStrings is preceded by a string
terminator.
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.base/examine-backward.c