> You want to use the libunwind that is built into linux unless it can unwind > when there is no EH frame info. > The remote unwind that we implemented that is used by LLDB will handle cases > where there is no EH frame > and it will disassemble the function and it will handle non-callsite > locations. The EH frame info built into binaries > is sparsely populated with info that is only valid at call sites which means > you can't use it to unwind the first frame, > nor any frame after a complete register state backup (sigtramp).
I see, that makes things more difficult. > We are about to replace the libunwind stack backtracing soon with a new stack > crawling engine that doesn't use > libunwind, so this issue will go away soon (this week hopefully). Nice! I will wait for said change then. In the meantime, i have started to push my patches to a git clone here http://gitorious.org/lldb/lldb-linux. Please feel free to pull from there, whatever you find useful. _______________________________________________ lldb-dev mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
