[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug binutils/27534] New: [readelf] .debug_addr reference not resolved f
From: |
vries at gcc dot gnu.org |
Subject: |
[Bug binutils/27534] New: [readelf] .debug_addr reference not resolved for split dwarf |
Date: |
Sat, 06 Mar 2021 08:36:19 +0000 |
https://sourceware.org/bugzilla/show_bug.cgi?id=27534
Bug ID: 27534
Summary: [readelf] .debug_addr reference not resolved for split
dwarf
Product: binutils
Version: 2.37 (HEAD)
Status: NEW
Severity: normal
Priority: P2
Component: binutils
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
Consider this test-case:
...
$ gcc ./src/gdb/testsuite/gdb.dwarf2/fission-multi-cu*.c -gsplit-dwarf
...
With
...
$ ~/binutils/install/bin/readelf -w -P a.out
...
we get:
...
Contents of the .debug_info.dwo section (loaded from
/home/vries/gdb_versions/devel/fission-multi-cu1.dwo):
<1><18>: Abbrev Number: 2 (DW_TAG_subprogram)
<19> DW_AT_name : (indexed string: 0x2): func
<20> DW_AT_low_pc : (addr_index: 0x0): <no .debug_addr section>
...
The address for func is:
...
$ nm a.out | grep func
0000000000400497 T func
...
which matches this entry in the .debug_addr table in a.out:
...
Contents of the .debug_addr section (loaded from a.out):
For compilation unit at offset 0xc7:
Index Address
0: 0000000000400497
...
So, we could actually print:
...
<20> DW_AT_low_pc : (addr_index: 0x0): 0x00400497
...
--
You are receiving this mail because:
You are on the CC list for the bug.
- [Bug binutils/27534] New: [readelf] .debug_addr reference not resolved for split dwarf,
vries at gcc dot gnu.org <=