On 10/31/2009 03:19 AM, John David Anglin wrote:
On Fri, 30 Oct 2009, John David Anglin wrote:
There seems to a problem with readelf -u on 32-bit kernels. The
address ranges are wrong. The segment offset doesn't seem to be
being handled correctly.
readelf -u uses the base address of the segment containing the
.PARISC.unwind section. On 64-bit kernels, the .PARISC.unwind
section is in the same segment as the .text section, so the
addresses print are correct. However, on recent 32-bit kernels,
this is not the case:
Section to Segment mapping:
Segment Sections...
00 .text .rodata .init.rodata __bug_table .pci_fixup .builtin_fw __ksymtab __ksymtab_gpl __kcrctab __kcrctab_gpl __ksymtab_strings __param
01 __ex_table .PARISC.unwind .data.read_mostly .data .got .data.vmpages .bss
02 .data.init_task .init.text .init.data .init.setup .initcall.init .con_initcall.init .exit.text
03
.PARISC.unwind is readonly, so it shouldn't be in a W segment.
apply the patch in http://patchwork.kernel.org/patch/55797/ before testing.
.PARISC.unwind is then still in a RW segment, but at least you will get more reliable output.
Helge
--
To unsubscribe from this list: send the line "unsubscribe linux-parisc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
