aboutsummaryrefslogtreecommitdiff
path: root/sim/m32c/gdb-if.c
diff options
context:
space:
mode:
authorGuinevere Larsen <blarsen@redhat.com>2023-12-14 10:52:29 +0100
committerGuinevere Larsen <blarsen@redhat.com>2024-01-22 11:42:27 +0100
commit06ceae57ed4031e8a11ad7556684e1ac83477d73 (patch)
treeddc08c02e838c73aa0c19b028c88e7f09e22790e /sim/m32c/gdb-if.c
parentb9bdebba83fafa4ad4a2328d00880410acd922aa (diff)
downloadbinutils-06ceae57ed4031e8a11ad7556684e1ac83477d73.zip
binutils-06ceae57ed4031e8a11ad7556684e1ac83477d73.tar.gz
binutils-06ceae57ed4031e8a11ad7556684e1ac83477d73.tar.bz2
gdb/testsuite: relax filename restriction in some gdb.btrace tests
The test gdb.btrace/tailcall.exp has multiple tests that include the filename in the output. When testing with gcc, only a relative path is printed, but when using clang, the full file path is printed instead. This makes most of those tests fail, with the exception of "record goto 4" which allows for more characters before the file name. The test gdb.btrace/recod_goto.exp suffers with the same issue This commit allows for text before the filename. However, instead of how the aforementioned "record goto 4", it uses a regexp that doesn't allow for newlines, just in case some off output happens. Approved-By: Tom Tromey <tom@tromey.com>
Diffstat (limited to 'sim/m32c/gdb-if.c')
0 files changed, 0 insertions, 0 deletions