aboutsummaryrefslogtreecommitdiff
path: root/gdb/interps.c
diff options
context:
space:
mode:
authorTom Tromey <tromey@adacore.com>2023-01-19 14:01:27 -0700
committerTom Tromey <tromey@adacore.com>2023-02-08 10:12:22 -0700
commitcdeb7b7de286078a1a0733a5cc9672c566917d61 (patch)
tree7918174991d17f66230f3a3b48f81e2fc953b812 /gdb/interps.c
parent300fa060abbfd8d36c81d8cc777ea1f32f07b4f0 (diff)
downloadbinutils-cdeb7b7de286078a1a0733a5cc9672c566917d61.zip
binutils-cdeb7b7de286078a1a0733a5cc9672c566917d61.tar.gz
binutils-cdeb7b7de286078a1a0733a5cc9672c566917d61.tar.bz2
Avoid FAILs in gdb.compile
Many gdb.compile C++ tests fail for me on Fedora 36. I think these are largely bugs in the plugin, though I didn't investigate too deeply. Once one failure is seen, this often cascades and sometimes there are many timeouts. For example, this can happen: (gdb) compile code var = a->get_var () warning: Could not find symbol "_ZZ9_gdb_exprP10__gdb_regsE1a" for compiled module "/tmp/gdbobj-0xdI6U/out2.o". 1 symbols were missing, cannot continue. I think this is probably a plugin bug because, IIRC, in theory these symbols should be exempt from a lookup via gdb. This patch arranges to catch any catastrophic failure and then simply exit the entire .exp file.
Diffstat (limited to 'gdb/interps.c')
0 files changed, 0 insertions, 0 deletions