This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug translator/11074] loc2c/vta: synthetic address range warning/error during -p4 for dwarf const_value
- From: "fche at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 9 Dec 2009 18:51:22 -0000
- Subject: [Bug translator/11074] loc2c/vta: synthetic address range warning/error during -p4 for dwarf const_value
- References: <20091209172439.11074.fche@redhat.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From fche at redhat dot com 2009-12-09 18:51 -------
It appears as though the const_value encoded in dwarf is a pointer to global
data in the kernel, and thus subject to relocation even though vmlinux is
ET_EXEC.
(gdb) p/x 3231800064
$1 = 0xc0a15b00
% nm -S vmlinux | sort| grep c0a1
...
c0a13a34 00000004 D x86_cpu_to_apicid_early_ptr
c0a13a38 00000004 D x86_bios_cpu_apicid_early_ptr
c0a13a40 00002d80 D contig_page_data
c0a167c0 00000498 d pci_serial_quirks
c0a16c58 00000014 d pcmcia_bus_interface
c0a16c6c 0000000c d cpufreq_cpu_notifier
...
So it's as if we must infer a need for _stp_relocate for
such values for the kernel, but probably only if the
dwarf type is that of a pointer. Ugh.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=11074
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.