[Top][All Lists]

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

RE: [libunwind] backtrace on EM64T

From: Yeshurun, Meir
Subject: RE: [libunwind] backtrace on EM64T
Date: Wed, 9 Nov 2005 12:52:53 +0200

Hi David, 

I can't commit to this, but I would like to try to fill in this hole.
Any additional guidelines that you can give me would be highly

Thanks a lot,

-----Original Message-----
From: address@hidden [mailto:address@hidden On Behalf Of
David Mosberger-Tang
Sent: Tuesday, November 08, 2005 10:23 PM
To: Arun Sharma
Cc: Yeshurun, Meir; Nathan Froyd; address@hidden
Subject: Re: [libunwind] backtrace on EM64T

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
> > 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
> > initialization phase in which the DWARF2 information will be read,
> > allow subsequent backtraces into the same objects to be done
> >
> 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]