search for: _unwind_backtrace

Hi all, I'm debugging a crash in the guts of libunwind that started occuring when I changed the ASan runtime to use _Unwind_Backtrace() on OSX to report errors. The crash happens for every test case that has an ASan report in it, so I'm suspecting something's wrong with the unwind info generated by the Xcode Clang, which I'm using to build my Clang and the ASan runtime library (with either -funwind-tables or -fasynchr...

...nf-winnt-rtlunwind https://docs.microsoft.com/en-us/windows/win32/api/winnt/nf-winnt-rtlunwind2 https://docs.microsoft.com/en-us/windows/win32/api/winnt/nf-winnt-rtlunwindex https://docs.microsoft.com/en-us/windows/win32/api/winnt/nf-winnt-rtlvirtualunwind ? > > For libbacktrace, I guess the _Unwind_Backtrace function in libunwind > might work and be useful, even if the rest of libunwind doesn't make sense > in such a context. Ian, please share your vision/propose some plan. > I haven't tested this function on windows though, and > it'd require you to fix the linker error one...

...lt;https://github.com/llvm/llvm-project/blob/master/libunwind/CMakeLists.txt#L294>, if the compiler “supports” it. >> > > Are you sure that libunwind being built without -funwind-tables is the > cause of the bug? Yep, pretty sure, I’ve found that the cause of the problem is the _Unwind_Backtrace function not executing the provided callback. It isn’t doing so because, since libunwind is compiled without the flag, the information about the stack frame is lost, so, when _Unwind_Backtrace looks for it, it can’t find it (since we’ve entered the _Unwind_Backtrace stack frame, which lives in libu...

...ect/blob/master/libunwind/CMakeLists.txt#L294, if the compiler “supports” it. >> >> >> Are you sure that libunwind being built without -funwind-tables is the >> cause of the bug? >> >> >> Yep, pretty sure, I’ve found that the cause of the problem is the _Unwind_Backtrace function not executing the provided callback. It isn’t doing so because, since libunwind is compiled without the flag, the information about the stack frame is lost, so, when _Unwind_Backtrace looks for it, it can’t find it (since we’ve entered the _Unwind_Backtrace stack frame, which lives in libu...

...ect/blob/master/libunwind/CMakeLists.txt#L294, if the compiler “supports” it. >> >> >> Are you sure that libunwind being built without -funwind-tables is the >> cause of the bug? >> >> >> Yep, pretty sure, I’ve found that the cause of the problem is the _Unwind_Backtrace function not executing the provided callback. It isn’t doing so because, since libunwind is compiled without the flag, the information about the stack frame is lost, so, when _Unwind_Backtrace looks for it, it can’t find it (since we’ve entered the _Unwind_Backtrace stack frame, which lives in libu...

...libunwind, among others because clang never generates code that uses arm-defined PRs for exceptions and cleanup, only for trivial frame unwinding (it always uses __gxx_personality_v0 for exceptions/cleanup), so I don't think today libunwind depends on libc++abi, except for the recent patch for _Unwind_Backtrace. Antoine > > On 10/22/14 11:39 AM, Renato Golin wrote: > > So, I remember we discussed this earlier this year, but I can't find the > thread. > > > > The idea is to move libunwind into compiler-rt for the simple reasons > below: > > > > 1. Unwinding...

...p/address-sanitizer/issues/detail?id=23) In order for exceptions to work correctly, it should be possible to unwind through the functions wrapped by ASan RTL (in particular, __cxa_throw()) Because we intentionally build the runtime with -fno-exceptions, we need at least the unwind tables to support _Unwind_Backtrace(). -- Alexander Potapenko Software Engineer Google Moscow -------------- next part -------------- A non-text attachment was scrubbed... Name: asan-unwind-tables.patch Type: text/x-patch Size: 391 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20111229/c2d7...

...s/windows/win32/api/winnt/nf-winnt-rtlunwind > > ex > > > https://docs.microsoft.com/en-us/windows/win32/api/winnt/nf-winnt-rtlvirtua > > lunwind > > ? > > Yes, those are the functions used for unwinding on windows. > > > For libbacktrace, I guess the _Unwind_Backtrace function in > > libunwind > > might work and be useful, even if the rest of libunwind doesn't > > make sense > > in such a context. > > Just FWIW, I made a RFC patch that fixes building libunwind in MSVC mode > (still requiring clang-cl t...

There’s this bug: https://bugs.llvm.org/show_bug.cgi?id=38468. I’ve managed to track it down to a configuration issue. The thing is that in order for libunwind to be usable on ARM Linux, it should be built with the -funwind-tables flag. This flag is conditionally set here: https://github.com/llvm/llvm-project/blob/master/libunwind/CMakeLists.txt#L294, if the compiler “supports” it. However, the

...the exception's stack trace). I'm assuming that the way to make this work is to modify the exception personality function to capture information about the stack. Unfortunately, none of my experiments in this area have yielded anything useful. For example, I have experimented with calling _Unwind_Backtrace from the personality function, but this only yields an _Unwind_Context pointer which is of limited use. It's hard to tell because most of the structures are opaque, but it appears as though the information I'm getting from _Unwind_Backtrace has little or no relation to the state of the stac...

...it this way is that it would be too expensive to always capture call frame information on every exception, so instead my compiler only uses the heavier personality function when the exception backtrace information is actually going to be used. Within the personality function, there's a call to _Unwind_Backtrace(), which walks through the list of call frames and calls a callback for each one. Within the callback, I can get the value of the return address for each call frame using _Unwind_GetIP(). So far so good. The problem is converting those addresses into meaningful symbols. For some reason that I don&...

...oking for backtrace -- Looking for backtrace - found -- backtrace facility detected indefault set of libraries -- Found Backtrace: /usr/include -- Performing TestC_SUPPORTS_WERROR_UNGUARDED_AVAILABILITY_NEW -- Performing TestC_SUPPORTS_WERROR_UNGUARDED_AVAILABILITY_NEW - Failed -- Looking for _Unwind_Backtrace -- Looking for _Unwind_Backtrace -found -- Looking for getpagesize -- Looking for getpagesize - found -- Looking for sysconf -- Looking for sysconf - found -- Looking for getrusage -- Looking for getrusage - found -- Looking for setrlimit -- Looking for setrlimit - found -- Looking for is...

...EnclosingFunction(void *pc) { ^ C:/Users/clang/libunwind/include\unwind.h:352:14: note: previous declaration is here extern void *_Unwind_FindEnclosingFunction(void *pc); ^ C:/Users/clang/libunwind/src/UnwindLevel1-gcc-ext.c:108:1: warning: redeclaration of '_Unwind_Backtrace' should not add 'dllexport' attribute [-Wdll-attribute-on-redeclaration] _Unwind_Backtrace(_Unwind_Trace_Fn callback, void *ref) { ^ C:/Users/clang/libunwind/include\unwind.h:307:28: note: previous declaration is here extern _Unwind_Reason_Code _Unwind_Backtrace(_Unwind_Trace_Fn, void *...

...;-static' option for compilation, I have the following error message. $ llvm-arm-gcc -o hello hello.c -static /home/wonjeon/CodeSourcery/Sourcery_G++_Lite/arm-none-linux-gnueabi/libc//usr/lib/libc.a(backtrace.o): In function `backtrace': backtrace.c:(.text+0x2c): undefined reference to `_Unwind_Backtrace' collect2: ld returned 1 exit status I have no problem for '-static' option with llvm-gcc for x86 and arm-none-linux-gnueabi-gcc with for ARM without llvm though. Can anyone help? Thanks, Won -------------- next part -------------- An HTML attachment was scrubbed... URL: <ht...

....8.6, 3.8.7, 3.8.8, 3.8.9, 3.8.10, 3.8.11 and 3.8.12 contain a listing of all the new features that were added and bugs fixed in the GlusterFS 3.8 stable release. ### Bugs addressed A total of 13 patches have been merged, addressing 8 bugs: * #1447523: Glusterd segmentation fault in ' _Unwind_Backtrace' while running peer probe * #1449782: quota: limit-usage command failed with error " Failed to start aux mount" * #1449941: When either killing or restarting a brick with performance.stat-prefetch on, stat sometimes returns a bad st_size value. * #1450055: [GANESHA] Add...

...ttribute is added to @_Z3foov() simply because the landingpad can catch the exception object. However, in my notation, only no-throw can be added to this function, and no-throw does not imply no-unwind. It is possible for @_Z3foov() to unwind the stack. For example, the function @_Z3barv() may call _Unwind_Backtrace() to get the backtrace. Besides, some optimization might make the situation even worse. AFAIK, most of the stack unwinding implementations rely on the value in the link register or the return address on the stack. However, there is an optimization in LLVM code generation which will not save the li...

Hallo all, I was trying to Build LLVM with the cmake option LLVM_ENABLE_MODULES just out of curiosity. I used the RELEASE_400/final tag. It didn't work as I almost expected. So I'm wondering if the modulemaps aren't maintained anymore? If they aren't maintained anymore, why aren't they removed and that cmake option also removed?

Hi, I'm trying to do a build and install on Windows 10 with Visual Studio 2015 Community Edition for the X86 and ARM targets, from the current release_40 branch. While compilation completes without error, the INSTALL target fails with the following error: 54> CMake Error at projects/compiler-rt/lib/builtins/cmake_install.cmake:34 (file): 54> file INSTALL cannot find 54>

...Looking for backtrace -- Looking for backtrace - found -- backtrace facility detected in default set of libraries -- Found Backtrace: /usr/include -- Performing Test C_SUPPORTS_WERROR_UNGUARDED_AVAILABILITY_NEW -- Performing Test C_SUPPORTS_WERROR_UNGUARDED_AVAILABILITY_NEW - Failed -- Looking for _Unwind_Backtrace -- Looking for _Unwind_Backtrace - found -- Looking for getpagesize -- Looking for getpagesize - found -- Looking for sysconf -- Looking for sysconf - found -- Looking for getrusage -- Looking for getrusage - found -- Looking for setrlimit -- Looking for setrlimit - found -- Looking for isatty -- L...

So, I remember we discussed this earlier this year, but I can't find the thread. The idea is to move libunwind into compiler-rt for the simple reasons below: 1. Unwinding is not exclusive to C++, nor exception handling. 2. Clang still includes libgcc_s and libgcc_eh when using compiler-rt (maybe eh isn't needed, but it was there for libgcc). 3. Testing the libunwind with libc++ on ARM is