On 06/25/2013 12:35 AM, Richard Henderson wrote:
> On 06/24/2013 12:37 AM, Vineet Gupta wrote:
>> Aha, I see what's happening. For historical reasons, ARC Linux kernel stack
>> unwinder relies on .debug_frame (vs. .eh_frame) for stack unwinding. Being
>> non
>> allocatable it would default to addr
On 06/24/2013 12:37 AM, Vineet Gupta wrote:
> Aha, I see what's happening. For historical reasons, ARC Linux kernel stack
> unwinder relies on .debug_frame (vs. .eh_frame) for stack unwinding. Being non
> allocatable it would default to address zero hence the orig absolute
> relocations
> would wo
On 06/24/2013 12:58 PM, Jakub Jelinek wrote:
> On most targets, .debug_* sections are placed at address 0, so absolute
> relocations are the same as relocations relative to the start of the
> section.
> [snipped]
>
> So, either .debug_* sections are placed at address 0 and then absolute
> relocatio
On Mon, Jun 24, 2013 at 12:43:15PM +0530, Vineet Gupta wrote:
> Pardon me if I sound dense (not really my area of expertise), wowever, the 2nd
> word in FDE above (@.Lframe0) is a direct reference to start of .debbug_frame
> shouldn't it be something like
>
> @.Lframe0 - @.Lframe0
>
> i.e. zero.
On 06/24/2013 12:33 PM, Jakub Jelinek wrote:
> On Mon, Jun 24, 2013 at 12:06:27PM +0530, Vineet Gupta wrote:
>> I had a question about interpretation of FDE's CIE_pointer field (for
>> .debug_frame)
>>
>> The spec say (from dwarf4 version although it really doesn't matter):
>>
>> "2. CIE_pointer (
On Mon, Jun 24, 2013 at 12:06:27PM +0530, Vineet Gupta wrote:
> I had a question about interpretation of FDE's CIE_pointer field (for
> .debug_frame)
>
> The spec say (from dwarf4 version although it really doesn't matter):
>
> "2. CIE_pointer (4 or 8 bytes, see Section 7.4)
> A constant offset
