aboutsummaryrefslogtreecommitdiff
path: root/bfd/cpu-m68k.c
diff options
context:
space:
mode:
authorLancelot SIX <lancelot.six@amd.com>2021-12-29 09:01:25 -0500
committerLancelot SIX <lancelot.six@amd.com>2022-01-04 09:30:01 -0500
commit0b1e7ee5b572abb465b8095d7f92d49eed91e215 (patch)
treec3be84ddb2ad4fcf44fdfbcd8011196c38af1f3f /bfd/cpu-m68k.c
parent40c01d1b3dbeb56b6220064504e431ba43725630 (diff)
downloadgdb-0b1e7ee5b572abb465b8095d7f92d49eed91e215.zip
gdb-0b1e7ee5b572abb465b8095d7f92d49eed91e215.tar.gz
gdb-0b1e7ee5b572abb465b8095d7f92d49eed91e215.tar.bz2
gdb/testsuite: fix inferior-clone.exp for native-extended-gdbserver
003aae076207dbf32f98ba846158fc32669ef85f (gdb: Copy inferior properties in clone-inferior) introduced a testcase that fails when testing with the native-extended-gdbserver board: Running ../gdb/testsuite/gdb.base/inferior-clone.exp ... FAIL: gdb.base/inferior-clone.exp: inferior 2: clone-inferior FAIL: gdb.base/inferior-clone.exp: inferior 3: clone-inferior The error is as follows: clone-inferior [New inferior 2] Added inferior 2 on connection 1 (extended-remote localhost:2346) (gdb) FAIL: gdb.base/inferior-clone.exp: inferior 2: clone-inferior This fails because the testcase only expect the 'Added inferior 2' part of the message. The 'on connection 1 [...]' part is unexpected. Fix by adjusting the testcase to a account for the possible trailing part of the message. Tested on x86_64-linux with native-extende-gdbserver and unix boards. Change-Id: Ie3d6f04c9ffe9cab1fbda8ddf4935ee09b858c7a
Diffstat (limited to 'bfd/cpu-m68k.c')
0 files changed, 0 insertions, 0 deletions