similar to: [LLVMdev] Generating a backtrace

Displaying 20 results from an estimated 400 matches similar to: "[LLVMdev] Generating a backtrace"

2020 Aug 15
5
Supporting libunwind on Windows 10 (32bit; 64bit) for MSVC and Clang
Hello. I was trying to compile https://github.com/llvm/llvm-project/tree/master/libunwind using: - MSVC - Clang I wasn't able to configure this project for using MSVC (directly or via clang-cl): >cmake -G Ninja -DLLVM_PATH="C:/Users/clang/llvm-project-10.0.1/llvm" -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX="C:\Users\clang\libunwind_llvm" ../libunwind --
2020 Jul 21
0
Errors observing when talloc-2.3.1 is cross compiled
Hi Team, We need freeradius-server-3.0.21 to be cross compiled for armv7 based Marvell switch. Toolchain: armv7-marvell-linux-gnueabi-LE_i686_20160226 host : arm-none-linux-gnueabi CC : arm-marvell-linux-gnueabi-gcc For that talloc is dependent library. Trying to cross compile talloc-2.3.1 to for our architecture with below command. ./configure --disable-python --enable-gccdeps
2016 Jun 30
3
Building LLVM under Cygwin32 fails
I am updating our out-of-tree copy of LLVM to track the head (revision #272991 specifically). I have it building successfully with VC++ 2013 and CMake v3.5.2 on Windows, and with GCC v4.8.5 and CMake v3.5.2 on CentOS; but when I try building on Windows using Cygwin32 I get the following build failures: [ 4%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/Signals.cpp.o In file
2018 May 14
1
Unable to build 'lld' on Mac OS 10.9
Hi All, I am trying to build the 'lld' linker on Mac OS 10.9, but during the build, I am getting the errors. Following are the steps that I have followed: 1.     I have downloaded the ‘llvm-stable’ source code from the following location:   https://github.com/llvm-mirror/llvm/tree/stable   2.     Machine details(on which llvm source code isbeing built) are as follows: $ sw_vers
2016 Jun 30
0
Building LLVM under Cygwin32 fails
Googling indicates that cygwin doesn't have that functionality. Or, at least, didn't in 2010, when someone asked about the same problem: https://cygwin.com/ml/cygwin/2010-01/msg00596.html "cygwin has only dlsym() not the SGI DL_info + dladdr() yet. clang just needs it to get the path for the CIndex dll. This should be possible with the code in the LLVM_ON_WIN32 section, and convert
2019 Sep 17
2
Building LLVM with LLVM with no dependence on GCC
Hi folks! I'm trying to get rid of any dependency on libgcc*, but without success so far. The following commands were executed on a freshliy installed and updated Ubuntu 16.04 LTS: === snip === sudo apt-get install build-essential libffi-dev cmake # see aptget.txt for packages installed sudo mv /usr/local /usr/local.orig git clone https://github.com/llvm/llvm-project.git cd llvm-project; git
2019 Sep 20
2
Building LLVM with LLVM with no dependence on GCC
Thus wrote David Demelier via llvm-dev: > Also you will need to add more options to the components. See for example: > > LIBCXX_CXX_ABI=libcxxabi > LIBCXX_USE_COMPILER_RT=On > LIBCXXABI_USE_LLVM_UNWINDER=On > LIBCXXABI_USE_COMPILER_RT=On > LIBCXX_HAS_GCC_S_LIB=Off > LIBUNWIND_USE_COMPILER_RT=On > > And as mentioned above > > CLANG_DEFAULT_CXX_STDLIB=libc++
2013 Jan 05
2
[LLVMdev] fail to compile my code on 3.2
hi, my old code compiles well on 3.1, but fails on 3.2. the compile error is like below. ... g++ -o vc main.o `llvm-config --libs all --ldflags` /usr/lib/libLLVMSupport.a(Signals.o): In function `PrintStackTrace(void*)': Signals.cpp:(.text+0x6c8): undefined reference to `dladdr' Signals.cpp:(.text+0x749): undefined reference to `dladdr' collect2: error: ld returned 1 exit status
2015 Sep 29
0
[PATCH 2/2] bios: Don't try to guess the sections alignment
From: Sylvain Gault <sylvain.gault at gmail.com> For the compression / decompression to succeed, the sections layout must be the same between the virtual memory and load memory. The section alignment was kept in sync by introducing aligment that should be greater or equal to the actual section alignment. This patch compute the load memory addresses of the sections so that the layout is the
2002 Sep 13
2
[LLVMdev] Linux-x86 Compatability
ISSUE: In Interpreter::getCurrentExecutablePath(), dladdr() is a Solarisism. Luckily, getCurrentExecutablePath isn't being currently used anywhere in lli. ACTION: Wrap the method contents with #ifdef __sun__ ... #else return ""; #endif. If this functionality is actually desired, it would be more portable to hack up main() to join getcwd() with basename(argv[0]) to find the
2010 Aug 23
1
[LLVMdev] Error Building LLVM on AIX 6
Dear Patrick, Documentation on some AIX routines to do the same thing can be found at http://publib.boulder.ibm.com/infocenter/comphelp/v8v101/index.jsp?topic=/com.ibm.xlcpp8a.doc/proguide/ref/dynamic_load.htm. Interestingly enough, the same page suggests that AIX does, in fact, support dlopen() and friends for POSIX compatibility. You might need to find out if there's a header file or a
2013 Jan 05
0
[LLVMdev] fail to compile my code on 3.2
On Sat, Jan 5, 2013 at 9:18 AM, Jun Koi <junkoi2004 at gmail.com> wrote: > hi, > > my old code compiles well on 3.1, but fails on 3.2. > the compile error is like below. > > > ... > g++ -o vc main.o `llvm-config --libs all --ldflags` > /usr/lib/libLLVMSupport.a(Signals.o): In function `PrintStackTrace(void*)': > Signals.cpp:(.text+0x6c8): undefined reference
2015 Sep 29
10
[PATCH 0/2] Fixes for gcc 5
From: Sylvain Gault <sylvain.gault at gmail.com> TL;DR: The section aligment in linker scripts messed-up the memory mapping needed for the compression / decompression to work. The bug with gcc 5 is not trivial, I'll do my best to explain it here. Basically, there are two memory mappings of the code. One in "virtual memory", and one in "load memory". The one in
2012 Jul 14
0
[LLVMdev] [llvm-commits] Dealing with a corrupted /proc/self/exe link
Chandler Carruth wrote: > On Fri, Jul 13, 2012 at 1:40 PM, Benjamin Kramer <benny.kra at gmail.com > <mailto:benny.kra at gmail.com>> wrote: > > > On 13.07.2012, at 21:39, Gabor Greif <gabor.greif at alcatel-lucent.com > <mailto:gabor.greif at alcatel-lucent.com>> wrote: > > > Benjamin Kramer wrote: > >> On 13.07.2012,
2010 Aug 22
2
[LLVMdev] Error Building LLVM on AIX 6
I get the following problem building LLVM 2.7 on AIX 6: gmake[1]: Entering directory `/home/home/ac/psimmons/llvm/llvm-2.7/lib/System' llvm[1]: Compiling Path.cpp for Release build In file included from Path.cpp:262: Unix/Path.inc: In static member function 'static llvm::sys::Path llvm::sys::Path::GetTemporaryDirectory(std::string*)': Unix/Path.inc:142: error: 'mkdtemp' was
2012 Jul 13
2
[LLVMdev] [llvm-commits] Dealing with a corrupted /proc/self/exe link
On Fri, Jul 13, 2012 at 1:40 PM, Benjamin Kramer <benny.kra at gmail.com>wrote: > > On 13.07.2012, at 21:39, Gabor Greif <gabor.greif at alcatel-lucent.com> > wrote: > > > Benjamin Kramer wrote: > >> On 13.07.2012, at 09:46, Gabor Greif <gabor.greif at alcatel-lucent.com> > wrote: > >> > >>> Hi all, > >>> >
2006 Jul 25
1
Managing backtrace
I''m writing a method_missing handler to "automagically" create assertions from predicate functions. So, for example, one use might be: assert_not_include ''joes@shmoe.com'', response.to -or- assert_include ''info@mydomain.com'', response.from The code is working properly, but when I trigger an assert, the backtrace shows something like:
2005 May 16
0
Add backtrace info in win32-service
Hi all, I think it would greatly aid service debugging if we added Ruby''s backtrace information if a Service.start fails. This would be lines 1251-1255: if(NULL == hSCService){ strcpy(error,ErrorDescription(GetLastError())); CloseServiceHandle(hSCManager); rb_raise(cServiceError,error); } I''m not sure exactly how to do it, though. Or do you think it should just be
2008 Nov 21
0
Backtrace for passing specs
Hi, I''m using example.implementation_backtrace in a custom formatter to get the path of the file a passing spec belongs to. Following rspec on github I saw that implementation_backtrace is now deprecated and replaced by example.backtrace. Sadly it always returns nil for passed specs. So I had a look at the source and found that backtrace only gets assigned if line_number was set. Can
2011 Oct 11
0
Is it recommended to let Asterisk run with "backtrace options"
Hi, On some systems, I can see sometimes that Asterisk crashed before being automatically restarted (by a watch guard script). To find the root cause of this, I'm wondering if I should let asterisk run for ever with "backtrace options" DEBUG_THREADS and DONT_OPTIMIZE turned on. Which negative side effect should prevent me from doing this ? What would you suggest ? Regards