[Top][All Lists]

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

Re: [libunwind] backtrace on EM64T

From: Arun Sharma
Subject: Re: [libunwind] backtrace on EM64T
Date: Mon, 21 Nov 2005 17:04:31 -0800
User-agent: Mozilla Thunderbird 1.0.7 (X11/20051011)

Keith Owens wrote:

I see that ia64 implements a script cache and there is no such thing on x86-64. Would it be correct to say that a dwarf2 based system should implement a cache of ip -> unw_proc_info_t mappings?

One problem with the ia64 unwind cache is that it uses kmalloc().  Code
expects to be able to call the unwinder when the system is running out
of memory or even from an NMI/MCA/INIT handler, at which point the slab
locks and chains are unreliable.  My KDB patches introduce a last ditch
allocator for the ia64 unwinder, so we can get backtraces even when the
entire system is dying.

Having a malloc anywhere in the unw_step() path is a deal killer for us.

Do you see this issue in libunwind as well? If yes, could you be more specific? Thanks.


reply via email to

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