diff options
author | Tom de Vries <tdevries@suse.de> | 2023-08-10 15:46:30 +0200 |
---|---|---|
committer | Tom de Vries <tdevries@suse.de> | 2023-08-10 15:46:30 +0200 |
commit | 698652da9364297319288293199cdb1f77d36466 (patch) | |
tree | c7edd3ec351ff2c6ed91c2523e3d67ad6d34609d | |
parent | 107ab8d45df84b442ce2d79c6dda3a9b3afc80d5 (diff) | |
download | gdb-698652da9364297319288293199cdb1f77d36466.zip gdb-698652da9364297319288293199cdb1f77d36466.tar.gz gdb-698652da9364297319288293199cdb1f77d36466.tar.bz2 |
[gdb/testsuite] Fix gdb.dwarf2/enqueued-cu-base-addr.exp with cc-with-gnu-debuglink
When running test-case gdb.dwarf2/enqueued-cu-base-addr.exp with target board
cc-with-gnu-debuglink, I run into:
...
(gdb) PASS: gdb.dwarf2/enqueued-cu-base-addr.exp: ptype foo
maint print symbols -objfile enqueued-cu-base-addr^M
(gdb) FAIL: gdb.dwarf2/enqueued-cu-base-addr.exp: CU addr found
...
The problem is that the CU we're trying to print is in objfile
enqueued-cu-base-addr.debug instead of enqueued-cu-base-addr.
Fix this by replacing "-objfile enqueued-cu-base-addr" with "-source cu2".
Tested on x86_64-linux.
-rw-r--r-- | gdb/testsuite/gdb.dwarf2/enqueued-cu-base-addr.exp | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gdb/testsuite/gdb.dwarf2/enqueued-cu-base-addr.exp b/gdb/testsuite/gdb.dwarf2/enqueued-cu-base-addr.exp index 9b2d1d8..c44cfd1 100644 --- a/gdb/testsuite/gdb.dwarf2/enqueued-cu-base-addr.exp +++ b/gdb/testsuite/gdb.dwarf2/enqueued-cu-base-addr.exp @@ -97,7 +97,7 @@ set cu2_blockvector_re \ "" \ "block #000, \[^\r\n\]* in ($hex)..$hex" \ ".*"] -gdb_test_multiple "maint print symbols -objfile $testfile" "CU addr found" { +gdb_test_multiple "maint print symbols -source cu2" "CU addr found" { -re -wrap $cu2_blockvector_re { set addr $expect_out(1,string) if { $addr eq "0x0" } { |