search for: crashrecoverycontext

By default, calls to abort() in the MS CRT do not trigger an exception and forcefully terminate the process, making CrashRecoveryContext not very useful on Windows for catching abort(), and consequently, assert(). One solution is to create a custom abort() handler that calls RaiseException(), which will be caught by the handler in CrashRecoveryContext. The relevant client-side code is: void win_abort_handler(int) { RaiseExcepti...

...ls/lib/Support -D_DEBUG -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -O3 -fomit-frame-pointer -fno-exceptions -fPIC -Woverloaded-virtual -Wcast-qual -Wall -W -Wno-unused-parameter -Wwrite-strings -c -MMD -MP -MF "<2ndStageObjDir>/BuildTools/lib/Support/Release+Asserts/CrashRecoveryContext.d.tmp" -MT "<2ndStageObjDir>/BuildTools/lib/Support/Release+Asserts/CrashRecoveryContext.o" -MT "<2ndStageObjDir>/BuildTools/lib/Support/Release+Asserts/CrashRecoveryContext.d" <LLVMSRC>/lib/Support/CrashRecoveryContext.cpp -o <2ndStageObjDir>/BuildT...

Where did getBacktrace go? I cant find any changes about it except for it simply disappearing after I updated from 3.8 to 4.0... -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170508/6ca7bce9/attachment.html>

...bin/../lib/gcc/x86_64-redhat-linux/4.7.2/../../../../include/c++/4.7.2/limits:1478:44: error: expected unqualified-id struct numeric_limits<unsigned __int128> ^ In file included from In file included from /home/fceldiener/vcs/llvm/lib/Support/CrashRecoveryContext.cpp:10: /home/fceldiener/vcs/llvm/lib/Support/DataStream.cpp:In file included from 18: 2) In file included from /home/fceldiener/vcs/llvm/include/llvm/Support/DataStream.h:/home/fceldiener/vcs/llvm/include/llvm/Support/CrashRecoveryContext.h20: In file included from /usr/bin/../lib/gcc/x86_64-r...

.../x86_64-linux-gnu/libstdc++.so.6.0.17) ==5926== by 0x6D4101B: llvm::sys::Path::Path(llvm::StringRef) (in /usr/lib/x86_64-linux-gnu/libLLVM-3.1.so.1) ==5926== by 0x4F4788C: ??? (in /usr/lib/libclang.so.1) ==5926== by 0x4F39080: ??? (in /usr/lib/libclang.so.1) ==5926== by 0x6D32DDE: llvm::CrashRecoveryContext::RunSafely(void (*)(void*), void*) (in /usr/lib/x86_64-linux-gnu/libLLVM-3.1.so.1) ==5926== by 0x6D32E13: ??? (in /usr/lib/x86_64-linux-gnu/libLLVM-3.1.so.1) ==5926== by 0x6D583CC: ??? (in /usr/lib/x86_64-linux-gnu/libLLVM-3.1.so.1) ==5926== by 0x7610E99: start_thread (pthread_create.c:308...

As part of my effort to replace our hand-rolled mutexes with std::mutex and std::recursive_mutex, I found that many of the tests were failing on Windows after doing the replacement. One of the reasons was due to the use of a mutex in lib\Support\CrashRecoveryContext.cpp. If this mutex is an std::recursive_mutex or std::mutex, tests fail. If this mutex is a windows CRITICAL_SECTION, the tests pass. I *think*, but am not 100% sure, that this is due to an interaction between MSVC's mutex implementation and the use of vectored exception handling. There is...

...hat's correct, it will >> probably need to be extended to handle non-fatal errors, warnings, >> suggestions, notes, etc. > > > Okay, it looks like the combination of llvm/Support/ErrorHandling.h and > LLVMContext::emitError solves a part of my use case.  I found the > CrashRecoveryContext class, which seems to allow me to intercept the > report_fatal_error() calls by installing a custom handler that writes to a > custom stream and then calls abort() instead of the default exit(). >  Alternatively, it looks like I can just spawn a thread for the LLVM work > and call pthre...

...y handle fatal errors. If that's correct, it will > probably need to be extended to handle non-fatal errors, warnings, > suggestions, notes, etc. > Okay, it looks like the combination of llvm/Support/ErrorHandling.h and LLVMContext::emitError solves a part of my use case. I found the CrashRecoveryContext class, which seems to allow me to intercept the report_fatal_error() calls by installing a custom handler that writes to a custom stream and then calls abort() instead of the default exit(). Alternatively, it looks like I can just spawn a thread for the LLVM work and call pthread_exit() instead of...

On Sun, 03 Jun 2012 12:12:06 -0700 Chris Lattner <clattner at apple.com> wrote: > > On Jun 2, 2012, at 11:01 AM, Mikael Lyngvig wrote: > > > If I may add my two cents: > > > > I am planning to use LLVM as the backend for a compiler I am > > working on. And I wholeheartedly agree with Justin that it is a > > problem, if LLVM is allowed to freely

...;> probably need to be extended to handle non-fatal errors, warnings, > >> suggestions, notes, etc. > > > > > > Okay, it looks like the combination of llvm/Support/ErrorHandling.h and > > LLVMContext::emitError solves a part of my use case. I found the > > CrashRecoveryContext class, which seems to allow me to intercept the > > report_fatal_error() calls by installing a custom handler that writes to > a > > custom stream and then calls abort() instead of the default exit(). > > Alternatively, it looks like I can just spawn a thread for the LLVM work...

2017-05-26 17:47 GMT-07:00 Zachary Turner via llvm-dev < llvm-dev at lists.llvm.org>: > Changing a header file somewhere and having to spend 10 minutes waiting > for a build leads to a lot of wasted developer time. > > The real culprit here is tablegen. Can we split support and ADT into two > - the parts that tablegen depends on and the parts that it doesn't? >

...eful stuff" and "narrowly useful stuff" > > Broadly useful stuff: > AlignOf > Allocator > ArrayRecycler > Atomic > AtomicOrdering > Capacity > Casting > Chrono > circular_raw_ostream > COM.h > CommandLine.h > Compiler.h > ConvertUTF.h > CrashRecoveryContext.h > DataExtractor.h > Debug.h > Endian.h > EndianStream.h > Errc.h > Errno.h > Error.h > ErrorHandling.h > ErrorOr.h > FileOutputBuffer.h > FileSystem.h > FileUtilities.h > Format*.h > GlobPattern.h > Host.h > JamCRC.h > KnownBits.h > LineIterat...

...t be useful outside of LLVM (and its subprojects)". > Broadly useful stuff: > AlignOf > Allocator > ArrayRecycler > Atomic > AtomicOrdering > Capacity > Casting > Chrono > circular_raw_ostream > COM.h > CommandLine.h > Compiler.h > ConvertUTF.h > CrashRecoveryContext.h > DataExtractor.h > Debug.h > Endian.h > EndianStream.h > Errc.h > Errno.h > Error.h > ErrorHandling.h > ErrorOr.h > FileOutputBuffer.h > FileSystem.h > FileUtilities.h > Format*.h > GlobPattern.h > Host.h > JamCRC.h > KnownBits.h > LineIterat...

...MakeFiles/LLVMSupport.dir/circular_raw_ostream.cpp.o CMakeFiles/LLVMSupport.dir/COM.cpp.o CMakeFiles/LLVMSupport.dir/CommandLine.cpp.o CMakeFiles/LLVMSupport.dir/Compression.cpp.o CMakeFiles/LLVMSupport.dir/ConvertUTF.c.o CMakeFiles/LLVMSupport.dir/ConvertUTFWrapper.cpp.o CMakeFiles/LLVMSupport.dir/CrashRecoveryContext.cpp.o CMakeFiles/LLVMSupport.dir/DataExtractor.cpp.o CMakeFiles/LLVMSupport.dir/DataStream.cpp.o CMakeFiles/LLVMSupport.dir/Debug.cpp.o CMakeFiles/LLVMSupport.dir/DeltaAlgorithm.cpp.o CMakeFiles/LLVMSupport.dir/DAGDeltaAlgorithm.cpp.o CMakeFiles/LLVMSupport.dir/Dwarf.cpp.o CMakeFiles/LLVMSupport.di...

Is there a simple method for compiling a custom assertion header/call into all the LLVM libraries? I want my application to be able to handle any thrown assertions (ie; as an exception) and recover or crash gracefully. I already have a custom header in place in the application's source, however this doesn't have an effect on [most of] the already compiled lib's. -------------- next

...e extended to handle non-fatal errors, warnings, >> >> suggestions, notes, etc. >> > >> > >> > Okay, it looks like the combination of llvm/Support/ErrorHandling.h and >> > LLVMContext::emitError solves a part of my use case.  I found the >> > CrashRecoveryContext class, which seems to allow me to intercept the >> > report_fatal_error() calls by installing a custom handler that writes to >> > a >> > custom stream and then calls abort() instead of the default exit(). >> >  Alternatively, it looks like I can just spawn a thr...

...Int.cpp for Release build llvm[1]: Compiling APSInt.cpp for Release build llvm[1]: Compiling Allocator.cpp for Release build llvm[1]: Compiling Atomic.cpp for Release build llvm[1]: Compiling CommandLine.cpp for Release build llvm[1]: Compiling ConstantRange.cpp for Release build llvm[1]: Compiling CrashRecoveryContext.cpp for Release build llvm[1]: Compiling DAGDeltaAlgorithm.cpp for Release build llvm[1]: Compiling Debug.cpp for Release build llvm[1]: Compiling DeltaAlgorithm.cpp for Release build llvm[1]: Compiling Disassembler.cpp for Release build llvm[1]: Compiling Dwarf.cpp for Release build llvm[1]: Compi...

....cpp for Release+Asserts build llvm[1]: Compiling CommandLine.cpp for Release+Asserts build llvm[1]: Compiling Allocator.cpp for Release+Asserts build llvm[1]: Compiling ConstantRange.cpp for Release+Asserts build llvm[1]: Compiling DAGDeltaAlgorithm.cpp for Release+Asserts build llvm[1]: Compiling CrashRecoveryContext.cpp for Release+Asserts build llvm[1]: Compiling Debug.cpp for Release+Asserts build llvm[1]: Compiling DeltaAlgorithm.cpp for Release+Asserts build llvm[1]: Compiling Dwarf.cpp for Release+Asserts build llvm[1]: Compiling ErrorHandling.cpp for Release+Asserts build llvm[1]: Compiling FileUtilities...

I've been guilty several times recently of committing code that introduced build warnings. It's a poor excuse, but my excuse is that I've been working on code for Windows and LLVM doesn't enable strict warnings by default on Windows and produces nearly half a million warnings (literally) if you manually turn them on. As such, I thought I'd make an effort to see what it would

...build > llvm[1]: Compiling CommandLine.cpp for Release+Asserts build > llvm[1]: Compiling Allocator.cpp for Release+Asserts build > llvm[1]: Compiling ConstantRange.cpp for Release+Asserts build > llvm[1]: Compiling DAGDeltaAlgorithm.cpp for Release+Asserts build > llvm[1]: Compiling CrashRecoveryContext.cpp for Release+Asserts build > llvm[1]: Compiling Debug.cpp for Release+Asserts build > llvm[1]: Compiling DeltaAlgorithm.cpp for Release+Asserts build > llvm[1]: Compiling Dwarf.cpp for Release+Asserts build > llvm[1]: Compiling ErrorHandling.cpp for Release+Asserts build > llvm[1]...