aboutsummaryrefslogtreecommitdiff
path: root/libctf/ctf-util.c
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2024-07-30 21:50:17 +0200
committerTom de Vries <tdevries@suse.de>2024-07-30 21:50:17 +0200
commit183bccfce1bf17673bf5f3d42f3ca8daee20ac73 (patch)
tree9168d3023a244ebf16882cd83902ec6e9953127a /libctf/ctf-util.c
parent4f165e008d4f0533804ea125e0eae19f1cc12f9d (diff)
downloadbinutils-183bccfce1bf17673bf5f3d42f3ca8daee20ac73.zip
binutils-183bccfce1bf17673bf5f3d42f3ca8daee20ac73.tar.gz
binutils-183bccfce1bf17673bf5f3d42f3ca8daee20ac73.tar.bz2
[gdb/testsuite] Fix regexp in gdb.ada/mi_var_access.exp some more
When running test-case gdb.ada/mi_var_access.exp on arm-linux (debian trixie), I run into: ... Expecting: ^(-var-create A_String_Access \* A_String_Access[ ]+)?((\^done,name="A_String_Access",numchild="[0-9]+",.*|\^error,msg="Value out of range.".*)[ ]+[(]gdb[)] [ ]*) -var-create A_String_Access * A_String_Access ^error,msg="Cannot access memory at address 0x4" (gdb) FAIL: gdb.ada/mi_var_access.exp: Create varobj (unexpected output) ... This is similar to the problem fixed by commit c5a72a8d1c3 ("[gdb/testsuite] Fix regexp in gdb.ada/mi_var_access.exp"). The problem in both cases is that we're printing an uninitialized variable, and consequently we can run into various error messages during printing. Fix this as in the other commit, by accepting the error message. Tested on arm-linux.
Diffstat (limited to 'libctf/ctf-util.c')
0 files changed, 0 insertions, 0 deletions