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

Greg Clayton wrote: > Not really. If you can send me a concrete example of something that isn't > working, it might help. Reporting progress. 1. `im loo -t` only ever finds one "best match", and the plist seems to have no effect on it. 2. The plist parsing code does get executed. I checked

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

Greg, Greg Clayton wrote: > Note that for C++ we get the fully qualified name and we pass in an empty > Declaration() so they all will compare to the same thing. This would solve > our current issue. We would also need to add the items to this map in the > same way: for

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

Okay, I'm stuck again. Let's back up and see what's happening: ~/src$ git clone llvm/ ~/src$ mkdir llvm-build/ ~/src/llvm-build$ cmake -GNinja -DCMAKE_BUILD_TYPE=Debug ../llvm ~/src/llvm-build$ ninja Now, ~/src/llvm-build/lib/libLLVMCore.a contains DWARF information that points to files

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

I guess LLDB was just helping your resolve build issues and make your product better... :-) Let us know how things go once you get your build fixed. Greg > On Oct 23, 2015, at 9:45 AM, Ramkumar Ramachandra wrote: > > Hi, > > On Wed, Oct 21, 2015 at 2:27 PM, Greg Clayton

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

On Tue, Oct 20, 2015 at 8:22 PM, Greg Clayton wrote: > Then try running and let me know what your results are! Hm, there seems to be something seriously wrong. I triple-checked everything, but Declaration::Compare is not even called when the error is triggered! How should we

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

So first, an addendum: I found a way to make the project build without using a symlink, and use a direct reference instead. The problem still persists. It may be that symlink is one of the problems, but it is certainly not the only problem. On Tue, Oct 20, 2015 at 8:22 PM, Greg Clayton

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

I seen very similar error messages when debugging an application compiled with fission (split/dwo) debug info on Linux with a release version of LLDB compiled from ToT. When I tested the same with a debug or with a release+assert build I hit some assertion inside clang. It might worth a try to

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

Alright, let's try to fix the bug. Let's work backward from the leaves: clang's ASTImporter.cpp:2979 and AstImporter.cpp:3044. In the backtrace, what seems to be most relevant is a call inside layoutRecordType, namely ClangASTSource.cpp:1709. The codebase clearly shows efforts to emit "Please

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

> On Oct 16, 2015, at 3:01 PM, Ramkumar Ramachandra wrote: > > Alright, let's try to fix the bug. > > Let's work backward from the leaves: clang's ASTImporter.cpp:2979 and > AstImporter.cpp:3044. In the backtrace, what seems to be most relevant > is a call inside

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?] Confusion between translation units?

Hi, At one point in the debugging session, I get this when I try to print a particular value: error: field '__r_' declared with incompatible types in different translation units ('std::__1::__compressed_pair::__rep,

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

In LLDB we create clang::ASTContext objects for the modules (executable and shared libraries), one for the target to contain the expression results, and one for each expression. When we evaluate an expression we might do something like: (lldb) expr a + b where "a" is from liba.so and "b" is