[Top][All Lists]

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

Re: [libunwind] backtrace on EM64T

From: David Mosberger-Tang
Subject: Re: [libunwind] backtrace on EM64T
Date: Tue, 8 Nov 2005 12:23:28 -0800

On 11/8/05, Arun Sharma <address@hidden> wrote:
> Yeshurun, Meir wrote:
> > Thanks for the quick reply, Nathan.
> >
> > I don't know much about DWARF2 unwind information (yet). Suppose however
> > that you are backtracing many times into code from the same set of
> > shared or executable objects. Is it possible to limit the penalty to an
> > initialization phase in which the DWARF2 information will be read, and
> > allow subsequent backtraces into the same objects to be done quickly?
> >
> I can't seem to find a noticable improvement.

That's because caching has not been implemented yet for DWARF2 (it is,
for the ia64 unwinder and makes a huge difference).  The code is
already set up to handle caching, but somebody would have to fill in
the actual code...

Mosberger Consulting LLC, voice/fax: 510-744-9372,
35706 Runckel Lane, Fremont, CA 94536

reply via email to

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