search for: libbacktrac

Displaying 10 results from an estimated 10 matches for "libbacktrac".

Did you mean: libbacktrace
2014 Nov 20
3
[LLVMdev] Proposal: add Go frontend subproject based on llgo
...e: > On Wed, Nov 19, 2014 at 01:53:17PM -0800, Peter Collingbourne wrote: > > llgo depends on certain third-party components, namely a copy of the Go > > standard library (libgo), a Go program analysis library (go.tools) and two > > library dependencies of the standard library (libbacktrace and libffi). > > I think providing a better alternative to libffi is already a goal of > some people, but what is libbacktrace needed for? What is not provided > by the Itanium Unwind ABI? According to the libbacktrace readme file: > As of September 2012, libbacktrace only suppor...
2020 Aug 15
5
Supporting libunwind on Windows 10 (32bit; 64bit) for MSVC and Clang
...ect > > the > > symbols to use the MSVC C++ name mangling, so there's an > > undefined > > reference. > > > > > > I see, thanks. > > > > Which options exist for MSVC, in sense an alternative to libunwind and > > libbacktrace ? > > Well for libunwind, there's really no use for it in an MSVC setting. All > the unwinding functionality is already built into the operating system, > available via the Rtl*Unwind* functions. > Martin, you mean these functions https://docs.microsoft.com/en-us/windows/win32/...
2020 Aug 16
3
Supporting libunwind on Windows 10 (32bit; 64bit) for MSVC and Clang
...; > > undefined > > > reference. > > > > > > > > > I see, thanks. > > > > > > Which options exist for MSVC, in sense an alternative to > > libunwind and > > > libbacktrace ? > > > > Well for libunwind, there's really no use for it in an MSVC > > setting. All > > the unwinding functionality is already built into the operating > > system, > > available via the Rtl*Unwind* functions. > > > &...
2014 Nov 19
14
[LLVMdev] Proposal: add Go frontend subproject based on llgo
...other subprojects as llgo is written in Go and depends on the Go bindings previously contributed to LLVM. llgo depends on certain third-party components, namely a copy of the Go standard library (libgo), a Go program analysis library (go.tools) and two library dependencies of the standard library (libbacktrace and libffi). These would be mirrored into the llgo repository under a third_party directory. They would retain their original licenses, which are BSD and GPLv3 with Runtime Library Exception (the latter only applies to a handful of header files; eventually we would seek to replace these). As a fi...
2014 Nov 25
2
[LLVMdev] [llgo-dev] Re: Proposal: add Go frontend subproject based on llgo
...nd depends on the Go bindings previously contributed to LLVM. > > > > llgo depends on certain third-party components, namely a copy of the Go > > standard library (libgo), a Go program analysis library (go.tools) and > two > > library dependencies of the standard library (libbacktrace and libffi). > These > > would be mirrored into the llgo repository under a third_party > directory. They > > would retain their original licenses, which are BSD and GPLv3 with > Runtime > > Library Exception (the latter only applies to a handful of header files; > &g...
2018 Mar 20
3
[LLD/ELF] - Should we implement .note.gnu.property and/or Intel CET in LLD ?
...inker should generate a IBT-enabled PLT together with a second PLT. That is also what is implemented in bfd it seems: https://sourceware.org/ml/binutils/2017-06/msg00285.html. GCC started to support it recently and already uses it for building libobjc, libgfortran, libmpx, libstdc++-v3, libatomic, libbacktrace and other libs: * https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=3c0f15b4cebccdbb6388a8df5933e69c9b773149 * https://gcc.gnu.org/git/?p=gcc.git&a=search&h=743b05ae4918eac3437965016649b2cabbdbb819&st=commit&s=intel+cet Technology is backwards compatible. I used GCC version 8.0.1 2018...
2018 Mar 20
0
[LLD/ELF] - Should we implement .note.gnu.property and/or Intel CET in LLD ?
...te a IBT-enabled PLT > together with a second PLT. That is also what is implemented in bfd it seems: > https://sourceware.org/ml/binutils/2017-06/msg00285.html. > GCC started to support it recently and already uses it for building > libobjc, libgfortran, libmpx, libstdc++-v3, libatomic, libbacktrace and other libs: > * https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=3c0f15b4cebccdbb6388a8df5933e69c9b773149 > * https://gcc.gnu.org/git/?p=gcc.git&a=search&h=743b05ae4918eac3437965016649b2cabbdbb819&st=commit&s=intel+cet > > Technology is backwards compatible. I used GCC...
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 --
2019 May 03
4
[LLD] Should --compress_debug_sections be enabled (=zlib) by default ?
Hi, In the file lld/ELF/Driver.cpp in function getCompressDebugSections we can see that the current default for lld is no debug section compression. It looks like tools like gdb, valgrind, elfutils, gcc's backtrace lib currently support compressed symbols. Since perf can use libdw from elfutils, I guess it supports it too. Do you think it's time to enable compressed debug section by
2023 Nov 12
1
Segmentation fault early in compilation of revision 85514
....o] Error 1 (ignore d) make[5]: [C:\rtools43\tmp\ccUw2zA8.mk:99: C:\rtools43\tmp\ccKMP0O7.ltrans32.ltrans.o] Error 1 (ignore d) during RTL pass: expand ../extra\trio/trio.c: In function 'TrioPower': ../extra\trio/trio.c:1261:1: internal compiler error: Segmentation fault 1261 | } | ^ libbacktrace could not find executable to open Please submit a full bug report, with preprocessed source (by using -freport-bug). See <https://gcc.gnu.org/bugs/> for instructions. make[5]: *** [C:\rtools43\tmp\ccUw2zA8.mk:197: C:\rtools43\tmp\ccKMP0O7.ltrans65.ltrans.o] Error 1 lto-wrapper.exe: fatal err...