Re: Out of order unwind entry warning

From: John David Anglin <dave@hiauly1.hia.nrc.ca>
To: Helge Deller <deller@gmx.de>
Cc: dave.anglin@nrc-cnrc.gc.ca, linux-parisc@vger.kernel.org,
	carlos@systemhalted.org, randolph@tausq.org
Subject: Re: Out of order unwind entry warning
Date: Fri, 30 Oct 2009 22:19:26 -0400	[thread overview]
Message-ID: <20091031021925.GA425@hiauly1.hia.nrc.ca> (raw)
In-Reply-To: <20091031004132.CA8C34FE3@hiauly1.hia.nrc.ca>

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.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)