aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2024-01-18 11:14:19 +0100
committerTom de Vries <tdevries@suse.de>2024-01-18 11:14:19 +0100
commite3e640b1cfac8dd8bcd7f0b730ded101a733bf76 (patch)
tree72e9c002a2ed9d39856d55d504bc5f85612e1915
parent48157d30b6c7ba955c5bc83b82f645531905285a (diff)
downloadbinutils-e3e640b1cfac8dd8bcd7f0b730ded101a733bf76.zip
binutils-e3e640b1cfac8dd8bcd7f0b730ded101a733bf76.tar.gz
binutils-e3e640b1cfac8dd8bcd7f0b730ded101a733bf76.tar.bz2
[gdb/testsuite] Call ldd --version in gdb.testsuite/dump-system-info.exp
Once in a while I'm looking at the gdb.log of an entire testsuite run, and I'm trying to establish what glibc version is used. Sometimes this is possible, sometimes not. Make this easy by calling ldd --version in test-case gdb.testsuite/dump-system-info.exp, which for instance on openSUSE Leap 15.4 gives: ... $ ldd --version ldd (GNU libc) 2.31 ... $ ... Tested on x86_64-linux. Approved-By: Tom Tromey <tom@tromey.com>
-rw-r--r--gdb/testsuite/gdb.testsuite/dump-system-info.exp1
1 files changed, 1 insertions, 0 deletions
diff --git a/gdb/testsuite/gdb.testsuite/dump-system-info.exp b/gdb/testsuite/gdb.testsuite/dump-system-info.exp
index 72f90f0..353f366 100644
--- a/gdb/testsuite/gdb.testsuite/dump-system-info.exp
+++ b/gdb/testsuite/gdb.testsuite/dump-system-info.exp
@@ -36,3 +36,4 @@ proc dump_info {cmd {what ""}} {
dump_info "cat /proc/cpuinfo" "Cpuinfo"
dump_info "uname -a"
dump_info "lsb_release -a"
+dump_info "ldd --version"