aboutsummaryrefslogtreecommitdiff
path: root/gdb/gdbserver/ChangeLog
diff options
context:
space:
mode:
authorSimon Marchi <simon.marchi@ericsson.com>2017-03-13 18:02:08 -0400
committerSimon Marchi <simon.marchi@ericsson.com>2017-03-13 18:02:08 -0400
commit7978d7c385b072a344d969f71cdc68e1a1171ec2 (patch)
tree19eaf070a035c53c51b47363a7b76a065783b902 /gdb/gdbserver/ChangeLog
parent896c0c1edee117ea333c66b1adac8c6f4def3f2b (diff)
downloadgdb-7978d7c385b072a344d969f71cdc68e1a1171ec2.zip
gdb-7978d7c385b072a344d969f71cdc68e1a1171ec2.tar.gz
gdb-7978d7c385b072a344d969f71cdc68e1a1171ec2.tar.bz2
testsuite: Disable backslash_in_multi_line_command_test for old DejaGnus
I noticed that backslash_in_multi_line_command_test in gdb.base/commands.exp failed on our RHEL6 servers. I traced it to the old version of DejaGnu (1.4.4). I have found that instead of receiving the expected: "print \\\nargc\n" gdb received: "print argc\n" thus breaking the test and its purpose. Versionof DejaGnu < 1.5 mess up sending "\\\n", it somehow gets replaced with a space. I found that the following commit in DejaGnu fixed the issue: http://git.savannah.gnu.org/cgit/dejagnu.git/commit/lib/remote.exp?id=3f39294f5cd6802858838d3bcc0ccce847ae17f2 Even though the commit is almost 10 years old, the following release of DejaGnu was only in 2013, which is why we still have systems with the old code. If the DejaGnu version is < 1.5, we just skip the test. gdb/testsuite/ChangeLog: * gdb.base/commands.exp (backslash_in_multi_line_command_test): Skip for versions of DejaGnu < 1.5.
Diffstat (limited to 'gdb/gdbserver/ChangeLog')
0 files changed, 0 insertions, 0 deletions