diff options
author | Tom de Vries <tdevries@suse.de> | 2022-10-10 14:44:40 +0200 |
---|---|---|
committer | Tom de Vries <tdevries@suse.de> | 2022-10-10 14:44:40 +0200 |
commit | ed6cd15957b80502410b771e080a88b2e4c949dd (patch) | |
tree | 1a13d3fffc9bfa1a726641cb7e5b3e2494d92cf6 /gdb/target-float.c | |
parent | 66984afd29ea9bad2155ed21098437a71208a106 (diff) | |
download | binutils-ed6cd15957b80502410b771e080a88b2e4c949dd.zip binutils-ed6cd15957b80502410b771e080a88b2e4c949dd.tar.gz binutils-ed6cd15957b80502410b771e080a88b2e4c949dd.tar.bz2 |
[gdb/testsuite] Fix error message for cmd with trailing newline
I noticed that the error message in gdb_test_multiple about trailing newline
in a command does not mention the offending command, nor the word command:
...
if [string match "*\[\r\n\]" $command] {
error "Invalid trailing newline in \"$message\" test"
}
...
Fix this by using instead:
...
error "Invalid trailing newline in \"$command\" command"
...
Also add a test-case to trigger this: gdb.testsuite/gdb-test.exp.
Tested on x86_64-linux.
Diffstat (limited to 'gdb/target-float.c')
0 files changed, 0 insertions, 0 deletions