similar to: [LLVMdev] [LLDB] build over linux

I find the lldb cannot display structure type information, such as "print ArgLocs.size()" as follows, -> 593 CCValAssign &VA = ArgLocs[i]; 594 EVT ValVT = VA.getValVT(); 595 ISD::ArgFlagsTy Flags = Ins[i].Flags; 596 bool IsRegLoc = VA.isRegLoc(); (lldb) print ArgLocs.size() error: call to a function

Hello, Just a quick refresh, on llvm.org/apt/ [1], I am rebuilding the sources of LLVM to create snapshot packages for the stable branches and development branches (currently, 3.4, in the hope of point releases and 3.5). This currently targets 2 releases of Debian and 4 of Ubuntu [2] and the llvm toolchain is built using the compiler shipped with the distribution. Following the recent

On Wed, Dec 21, 2016 at 2:55 PM, Teresa Johnson <tejohnson at google.com> wrote: > I think you can get this via "ninja -t commands bin/lldb-argdumper" > (this will give you a lot of output, all of the compilation commands > used to build that target). Or redo the build with -v to be sure. Unfortunately the old build tree is gone for space reclaim reasons. Sorry, I'll

Looks like your lldb is being compiled in C++11 mode and your llvm wasn't perhaps? -eric On Sat, Nov 23, 2013 at 12:57 AM, Marc Driftmeyer <mjd at reanimality.com> wrote: > Linking CXX executable ../../../../bin/lldb > Scanning dependencies of target lldb-platform > [100%] Building CXX object > tools/lldb/tools/lldb-platform/CMakeFiles/lldb-platform.dir/lldb-platform.cpp.o

Linking CXX executable ../../../../bin/lldb Scanning dependencies of target lldb-platform [100%] Building CXX object tools/lldb/tools/lldb-platform/CMakeFiles/lldb-platform.dir/lldb-platform.cpp.o *../../../../lib/liblldb.so.3.5: undefined reference to `llvm::SmallPtrSetImpl::SmallPtrSetImpl(void const**, unsigned int, llvm::SmallPtrSetImpl&&)'** **clang: error: linker command

This may be a debug info bug, if you could reduce it down a bit and file a bug that'd be appreciated. Thanks. -eric On Sun, Jan 27, 2013 at 12:11 AM, Jonathan <gamma_chen at yahoo.com.tw> wrote: > I find the lldb cannot display structure type information, such as "print > ArgLocs.size()" as follows, > > -> 593 CCValAssign &VA = ArgLocs[i]; >

On Tue, Dec 20, 2016 at 11:05 AM, Carsten Mattner <carstenmattner at gmail.com> wrote: > On Tue, Dec 20, 2016 at 5:05 PM, Teresa Johnson <tejohnson at google.com> > wrote: > > Hi Carsten, > > > > A few responses below, but first, can you get the link command for > > lldb.so.3.9.1? Last time it was the lldb.so build that was using > > ld.bfd with the

Hi everyone, I'm working on a library for runtime introspection of C++ programs, for example, getting stack traces, decorating logs with source file information, etc. It currently uses LLVMObject and LLVMDebugInfo. There's a feature I want to add, but it requires that I understand where on the stack local variables are located. For this to work on x86-64, I would need to do whole

After some thinking on this idea, it would not work because I need / want to use Debian/Ubuntu package to do the build and clang 3.4 is not built on these architecture :( So, if I bootstrap clang 3.4, I will have a dependency on libstdc++ 4.8... :/ On 25/12/2013 22:23, Arnaud Allard de Grandmaison wrote: > Hi Sylvestre, > > The easiest is probably to have a dependency to (and use)

On Tue, Apr 25, 2017 at 8:36 PM, Vedant Kumar via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > > On Apr 25, 2017, at 12:24 PM, Scott Smith <scott.smith at purestorage.com> > wrote: > > > > well, top-of-branch lldb uses this code, that's how I found it. Do you > mean libc++'s demangler? > > Thanks for explaining, this is the first time

Ten days ago, I asked "Can I debug llvm source code by iMac Xcode?". I still cannot do it now, but I can debug llvm source code by iMac lldb. I write it down on section  "1.4  Create LLVM.xcodeproj of supporting cpu0 by terminal cmake command" of GammaLLVMBackendBook.pdf in https://www.dropbox.com/sh/2pkh1fewlq2zag9/r9n4gnqPm7  Best regards Jonathan

Hi, all A few days ago I built lldb 3.3 release on our workstation with redhat enterprise linux 6.3 x86_64 (gcc verison 4.8.2). At the very beginning, lldb seemd to work and I debugged small native programs. Still, the bug showed itself randomly as follows: 1. at first, "(lldb)" prompt is missing and input from keyboard is not printed out, which means whatever I type, I can not read

I'm trying to build llvm and clang release_34 git branch on ubuntu 13.04, using cmake, and i'm getting numerous errors from lldb: [ 83%] Building CXX object tools/lldb/source/Core/CMakeFiles/lldbCore.dir/Address.cpp.o /home/sam/src/llvm/tools/lldb/source/Expression/ClangExpressionParser.cpp: In function ‘clang::FrontendAction* CreateFrontendBaseAction(clang::CompilerInstance&)’:

Dear, I would like build lldb on linux but i fail, (thanks for any help): 1/ get llvm3.0 2/ get clang.3.0 and put it into llvm/tools/ 3/ checkout lldb rev 144573 put into llvm/tools/ build --------------------------------- $ ./configure --disable-assertions \ --enable-debug-runtime \ --enable-jit \ --enable-libffi \ --enable-shared $ make REQUIRES_RTTI=1 VERBOSE=1

You should be able to create an xcode project using cmake and then use that to build and debug llvm (as you've discovered how to create an xcode project). Doug may know more. -eric On Sun, Nov 4, 2012 at 4:36 AM, gamma_chen <gamma_chen at yahoo.com.tw> wrote: > Ten days ago, I asked "Can I debug llvm source code by iMac Xcode?". I > still cannot do it now, but I can

On 28 Jul 2016, at 08:59, Renato Golin <renato.golin at linaro.org> wrote: > > On 28 Jul 2016 8:36 a.m., "David Chisnall via llvm-dev" <llvm-dev at lists.llvm.org> wrote: > > This does not apply to libc++. We support building the entire LLVM suite with other C++ standard library implementations (at least libstdc++, and I think also with Visual Studio’s

+ Jonas who hit the same bug recently. On Wed, May 16, 2018 at 8:01 AM, Eric Gorr via llvm-dev <llvm-dev at lists.llvm.org> wrote: > I was just trying to build lldb-6.0 from source (and had previously > successfully build llvm-6.0, clang-6.0, and lld-6.0 from source), but > received a compile error while using both just cmake and cmake+ninja > > Does this look familiar to

Can you please list the missing MI commands? This would be very valuable to both future contributors and also to the users of the LLDB MI. Thanks! On Mon, Aug 13, 2018 at 11:28 AM, Александр Поляков <polyakov.alx at gmail.com> wrote: > Thank you, Leonard, > I'm going to keep contributing to LLVM, so I think this is not the end! > > On Mon, Aug 13, 2018 at 8:15 PM Leonard

Nice to see great progress in this area! On Sun, Aug 12, 2018 at 2:49 PM, Александр Поляков via lldb-dev < lldb-dev at lists.llvm.org> wrote: > Hi LLVM folks, > > During this summer I was working on re-implementing of lldb-mi to > correctly use LLDB public API. You are welcome to read my final report > where I describe the contribution and challenges I faced with. > Link

I was just trying to build lldb-6.0 from source (and had previously successfully build llvm-6.0, clang-6.0, and lld-6.0 from source), but received a compile error while using both just cmake and cmake+ninja Does this look familiar to anyone? In file included from llvm/lldb-6.0.0.src/source/API/SystemInitializerFull.cpp:89: In file included from