projects / binutils-gdb.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 51794af) | patch
subst.exp: Empty message (3rd parameter) in call to gdb_test
authorJoel Brobecker <brobecker@gnat.com>
Mon, 31 May 2010 23:20:20 +0000 (23:20 +0000)
committerJoel Brobecker <brobecker@gnat.com>
Mon, 31 May 2010 23:20:20 +0000 (23:20 +0000)
commitf629457da977b54779bc4f22840b88e45dc302ea
treec25bf4a506056ebbd1755015a98584a28a307365tree
parent51794af883a67afadd94feec6b7f509f883c1094commit | diff
subst.exp: Empty message (3rd parameter) in call to gdb_test

This is something that Michael spotted and reported to me. Definitely
a mistake, causing the test to report no status...

gdb/testsuite:
2010-05-31  Joel Brobecker  <brobecker@adacore.com>

        * gdb.base/subst.exp: Fix call to gdb_test with empty message.

Tested on x86_64-linux.  The test now reports 30 PASSes instead of 29.
gdb/testsuite/ChangeLog diff | blob | history
gdb/testsuite/gdb.base/subst.exp diff | blob | history