| commit | e3e640b1cfac8dd8bcd7f0b730ded101a733bf76 | |
| author | Tom de Vries <tdevries@suse.de> | |
| Thu, 18 Jan 2024 10:14:19 +0000 (18 11:14 +0100) | ||
| committer | Tom de Vries <tdevries@suse.de> | |
| Thu, 18 Jan 2024 10:14:19 +0000 (18 11:14 +0100) | ||
| tree | 72e9c002a2ed9d39856d55d504bc5f85612e1915 | treesnapshot (tar.gz zip) |
| parent | 48157d30b6c7ba955c5bc83b82f645531905285a | commitdiff |
[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>
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>
| gdb/testsuite/gdb.testsuite/dump-system-info.exp | diffblobblamehistory |