aboutsummaryrefslogtreecommitdiff
path: root/gdb/block.c
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2024-06-10 10:43:10 +0200
committerTom de Vries <tdevries@suse.de>2024-06-10 10:43:10 +0200
commit3ee50921cb47f71c62b335cc36d1188e6b6ce1b3 (patch)
treeacadbb95181401976c0255974d7530cd8151f6b9 /gdb/block.c
parent1e3c814459d83247707f8c9840ac660726cfaae0 (diff)
downloadgdb-3ee50921cb47f71c62b335cc36d1188e6b6ce1b3.zip
gdb-3ee50921cb47f71c62b335cc36d1188e6b6ce1b3.tar.gz
gdb-3ee50921cb47f71c62b335cc36d1188e6b6ce1b3.tar.bz2
[gdb/testsuite] Don't use set auto-solib-add off
In test-case gdb.mi/mi-var-child-f.exp, we have: ... mi_gdb_test "-gdb-set auto-solib-add off" "\\^done" mi_runto prog_array mi_gdb_test "nosharedlibrary" ".*\\^done" ... This was added to avoid a name clash between the array variable as defined in gdb.mi/array.f90 and debug info in shared libraries, and used in other places in the testsuite. The same workaround is also used to ignore symbols from shared libraries when excercising for instance a command that prints all symbols. However, this approach can cause problems for targets like arm that require symbol info for some libraries like ld.so and libc to fully function. While absense of debug info for shared libraries should be handled gracefully (which does need fixing, see PR31817), failure to do so should not result in failures in unrelated test-cases. Fix this by removing "set auto-solib-add off". This ensures that we don't run into PR31817, while the presence of nosharedlibrary still ensures that in the rest of the test-case we're not bothered by shared library symbols. Likewise in other test-cases. Approved-by: Kevin Buettner <kevinb@redhat.com> Tested on arm-linux.
Diffstat (limited to 'gdb/block.c')
0 files changed, 0 insertions, 0 deletions