[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Libunwind-devel] [PATCH 3/5] Rework the lookup of the ARM specific

From: Arun Sharma
Subject: Re: [Libunwind-devel] [PATCH 3/5] Rework the lookup of the ARM specific unwind entry for local unwinding
Date: Mon, 8 Aug 2011 09:08:11 -0700

On Mon, Aug 8, 2011 at 7:41 AM, Ken Werner <address@hidden> wrote:
>> I'm a bit concerned about the arch-specific stuff getting added to
>> callback_data. What are the minimal arch specific hooks you need to
>> get this to work without an #ifdef UNW_TARGET_ARM? Something along the
>> lines of:
>> unw_dyn_info_t *di_tdep;
> I'm not sure I can follow. I agree that these ifdefs aren't very nice but
> what are the alternatives given the design of the libunwind API? The
> libunwind ARM backend could define its own tdep_find_proc_info but almost
> all of the code would be identical. It would walk the program headers using
> dl_iterate_phdr to collect the unw_dyn_info_t information and then call
> tdep_search_unwind_table to fill unw_proc_info_t.

Could we make just the callback from dl_iterate_phdr target dependent?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]