[lldb-dev] LLDB linux questions
gclayton at apple.com
Mon Sep 27 10:23:01 PDT 2010
That first line should have been:
You _don't_ want to use the libunwind that is built into linux...
On Sep 27, 2010, at 10:21 AM, Greg Clayton wrote:
> 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).
> 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).
> Until then, you will want to compile with our version of libuwnind that is statically linked into the lldb shared library.
> If you have a patch once you get this working, let us know and we will evaluate that patch.
> Let me know if you have any questions.
> Greg Clayton
> On Sep 27, 2010, at 10:01 AM, arvid.picciani at nokia.com wrote:
>>> Eli Freiman wrote the Makefile system. Presumably you're supposed to
>>> check out lldb into llvm/tools/lldb/ , and build from the root of the
>>> LLVM project. But I'm just guessing, I've never built it.
>> I see, thanks for that info. With the attached patch, it indeed seems to work for llvm from svn.<Makefile_llvm_git.patch>_______________________________________________
>> lldb-dev mailing list
>> lldb-dev at cs.uiuc.edu
> lldb-dev mailing list
> lldb-dev at cs.uiuc.edu
More information about the lldb-dev