This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFC]: append dwarf2 unwinder on sparc
- From: Tristan Gingold <gingold at adacore dot com>
- To: Mark Kettenis <mark dot kettenis at xs4all dot nl>
- Cc: gdb-patches at sourceware dot org
- Date: Wed, 2 Jul 2014 09:51:22 +0200
- Subject: Re: [RFC]: append dwarf2 unwinder on sparc
- Authentication-results: sourceware.org; auth=none
- References: <7E528836-0667-4A7E-B902-5F17D88F9221 at adacore dot com> <201407011600 dot s61G0G6J000433 at glazunov dot sibelius dot xs4all dot nl>
On 01 Jul 2014, at 18:00, Mark Kettenis <mark.kettenis@xs4all.nl> wrote:
>> From: Tristan Gingold <gingold@adacore.com>
>> Date: Tue, 1 Jul 2014 17:17:34 +0200
>>
>> Hello,
>>
>> as gcc 4.9 has switched to dwarf-4 by default, it now emits DW_OP_call_frame_cfa.
>> But gdb is able to handle it only if the frame was unwinded by dwarf2
>> (See dwarf2-frame.c:dwarf2_frame_cfa)
>>
>> Is there any reason not to append the dwarf2 unwinder on sparc ?
>
> Yes. The dwarf2 unwinder doesn't work properly with StackGhost. For
> Linux we append the dwarf2 unwinder in the OS/ABI-specific
> initialization function.
I see. My target was bareboard.
> On SPARC there is not much ambiuity about the call frame address.
> Perhaps it is time to lift the restriction in dwarf2_frame_cfa()?
I suppose this means adding a new method to struct frame_unwind ?
Not very exciting :-(
Thanks,
Tristan.