Re: [lldb-dev] [BUG?] Confusion between translation units?

Thanks for an excellent explanation. Unfortunately, -fno-limit-debug-info did not fix the problem; and that I don't see the problem with a gcc/gdb setup. So what I'm doing is forward-declaring LLVM IR entities (like `Value', `Type', `Function'), so that multiple downstream modules don't include

[lldb-dev] [Bug 25147] remove lldb-XXXXXX.expr temporary files when we are done with them

https://llvm.org/bugs/show_bug.cgi?id=25147 lab...@google.com changed: What|Removed |Added Assignee|lldb-dev@lists.llvm.org |lab...@google.com --- Comment #2 from

Re: [lldb-dev] incorrect shared library addresses

I have the same behavior with the system lldb and the one I build in xcode. My xcode is Version 6.4 (6E35b) I just hit command-b to build, is that what you mean? I don't really know xcode very well. On Tue, Oct 13, 2015 at 10:08 PM Todd Fiala wrote: > > Breakpoint 1:

Re: [lldb-dev] incorrect shared library addresses

I am guessing that your binary is missing a LC_VERSION_MIN_XXX load command and so it is being loaded with "-unknown-unknown" as the architecture. This is probably causing LLDB to load the DynamicLoaderStatic as the dynamic loader which just loads all shared libraries as the address that is

Re: [lldb-dev] LLDB: Unwinding based on Assembly Instruction Profiling

EH frame can't be used to unwind when we are in the first frame because it is only valid at call sites. It also can't be used in frames that are asynchronously interrupted like signal handler frames. So at frame zero, we typically just fall back to the default unwind plan for the current

[lldb-dev] [Bug 25172] New: TestBatchMode is flaky on linux

https://llvm.org/bugs/show_bug.cgi?id=25172 Bug ID: 25172 Summary: TestBatchMode is flaky on linux Product: lldb Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: normal

[lldb-dev] LLDB: Unwinding based on Assembly Instruction Profiling

Hi As far as I know, if the unwinding based on Assembly Instruction Profiling fails in LLDB then either EH frame unwinding or some other mechanism comes into picture to unwind properly. Am I right? In this case, should LLDB change the unwinder plan from Assembly Instruction Profiling to EH Frame