similar to: [LLVMdev] Runtime introspection of "Release Mode" programs using LLVM or LLDB

This might be a bit late, but I've got another argument for bundling zlib source with LLVM. Sanitizer tools need to symbolize stack traces in the reports. We've been using standalone symbolizer binary until now; sanitizer runtime spawns a new process as soon as an error is found, and communicates with it over a pipe. This is very cumbersome to deploy, because we need to keep another

You shouldn't need to use bitcode and opt -internalize to hide the symbols. You can do it with objcopy --localize-hidden like we did for DynamoRIO, but I assume you prefer this route because it ports nicely to Mac. :) On Tue, May 7, 2013 at 5:24 AM, Evgeniy Stepanov <eugeni.stepanov at gmail.com> wrote: > This might be a bit late, but I've got another argument for bundling >

Hi, Using master at b0a1c0b72c9c61f8b0a223e08f43498abb64f5e8, I cannot build LLVM. I configured with: CC=clang CXX=clang++ cmake -DCMAKE_INSTALL_PREFIX=$HOME/opt/llvm11-git \ -DCMAKE_BUILD_TYPE=Release \ -DLLVM_BUILD_LLVM_DYLIB=ON \ -DLLVM_LINK_LLVM_DYLIB=ON \ -DBUILD_SHARED_LIBS=OFF \ -DLLVM_ENABLE_EH=ON \ -DLLVM_ENABLE_RTTI=ON \

On Wed, Apr 17, 2013 at 12:37 AM, Chris Lattner <clattner at apple.com> wrote: > On Apr 16, 2013, at 11:53 AM, Eric Christopher <echristo at gmail.com> wrote: > > Historically we've done the former. The latter would require Chris > > wanting to do that. > > This case isn't so clearcut. We like to include libraries in the source > to make it easy to get

Reviving the discussion. The cool cmake-build of compiler-rt is not completely functional, but allows sanitizer runtimes to reuse LLVM code with almost no dirty hacks. Suppose I want to run call functions from LLVM libs (currently: LLVMDebugInfo, LLVMSupport) from sanitizer runtime. 1) I can simply include LLVM headers in sanitizer runtime, and it compiles and builds static asan runtime

On Apr 16, 2013, at 11:53 AM, Eric Christopher <echristo at gmail.com> wrote: > Historically we've done the former. The latter would require Chris > wanting to do that. This case isn't so clearcut. We like to include libraries in the source to make it easy to get up and running without having to install a ton of dependencies. However, this has license implications and is

Hi folks, Python2 has reached end of support[0], and many core Python packages are dropping pthon 2 support[1]. This is a subject that raises periodically on this mlist, with a rather strong no in 2018 [-1] and a slow move in 2019 [-2, -3]. Even if Python is not a core build requirement, it's used during some configurations steps (e.g. in the cmake export_executable_symbols function), for

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 to final report: https://apolyakov.github.io/GSoC-2018/ -- Alexander -------------- next part -------------- An HTML attachment was scrubbed... URL:

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

hi community, I would like to build lldb on linux but they are any documentation to do this.T hat is not the first time where someone does the same request. Please someone could show to me how to build with linux ? thanks a lot for your help

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

Is there any documentation on what machine interface (mi) commands are implemented in lldb-mi, and how compatible those commands are with gdb's mi? I'm asking for this project: https://github.com/cs01/gdbgui -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170310/667d44df/attachment.html>

AARRGGHH! Sometimes it's the simple things that are particularly frustrating, especially late at night.... Can anyone suggest a simple means for replacing all of the zero values in a matrix with NANs? I ended up writing an awk script to massage the input file, which works, of course, but is rather an inelegant blunt instrument. I'd prefer an R operation. I'm certain that

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

+llvmdev -llvm-dev On Mon, May 18, 2015 at 4:28 PM, Vince Harron <vince at nethacker.com> wrote: > Hi all, > > I would like to integrate crash reporting into Android developer tools, > starting with lldb and clang. Google Breakpad seems like a reasonable > option. > > https://code.google.com/p/google-breakpad/ > > Of course, it will only be enabled when the

Sorry if asked before. I'm new to LLDB, try to use it according to the lldb project site. I write some very simple code like: #include <stdio.h> int main(int argc, char **argv) { int counter = 0; while ( counter < 10 ) counter++; printf("counter: %d\n", counter); return 0; } and the session like: $ clang -g main.c $ lldb-3.4 a.out (lldb)

One more thing I want to note on this thread. For anyone looking at the patches. I’ve intentionally tried to make them minimal. After the patches have landed and stayed on trunk without issue for a while I’ll start doing cleanup around all the CMake version checks. I’d like to not open the flood gates on those kinds of cascading changes in case these patches need to be reverted for some reason.

Hi, I notice you're running a 32-bit program; are you also on a 32-bit host, or do you have a 64-bit OS installed? We don't generally test on 32-bit hosts, so it's possible you found a new bug. In addition, there are some known bugs with debugging 32-bit programs (even on 64-bit hosts) which will we hopefully be resolving soon. Nonetheless, I was unable to reproduce the behaviour you

It is interesting that the stop reason on the thread that stopped is "trace". That's what you would expect returning from the single-step to step over the breakpoint. But it looks like we got a signal while single-stepping, but the stop reason was misreported by somebody. Jim > On Apr 17, 2018, at 6:00 AM, Pavel Labath via lldb-dev <lldb-dev at lists.llvm.org> wrote: