swift-backtrace
swift-backtrace copied to clipboard
swift-server
💥 Backtraces for Swift on Linux and Windows
Docker 5.6.2-centos7 ``` > [builder 7/11] RUN swift build -c release --static-swift-stdlib: #13 1.577 Building for production... #13 1.738 In file included from /build/.build/checkouts/swift-backtrace/Sources/CBacktrace/elf.c:41: #13 1.738 /usr/include/unistd.h:1147:35: error: __block attribute...
Hello, First of all thanks for this tool, it would be amazing for me to have stack traces working on Linux. I'm trying to use it in a Raspberry pi...
Swift version 5.0 (swift-5.0-RELEASE) Target: armv6-unknown-linux-gnueabihf linker LOG: ``` $ swift build -c release -Xswiftc -g -v which clang /usr/local/bin/swiftc -sdk / -g -L /home/pi/Swish/ProjectFolder/.build/armv6-unknown-linux-gnueabihf/debug -o /home/pi/Swish/ProjectFolder/.build/armv6-unknown-linux-gnueabihf/debug/ProjectFolder -module-name Project -emit-executable...
It would be nice to support macOS in this library. As macOS comes with `libunwind` preinstalled that could make a good backend to use.
If a application runs into a stack overflow, this package doesn't print anything. Regarding to a message with @ianpartridge there are two issues: - [ ] swift-backtrace listens only on...
Hi, Just stumbled upon this library and the exact functionality I was looking for was `Backtrace.print()`. I see it's marked for deprecation on the next major version release? Any reason...
0x55ba62229212, Backtrace.(printBacktrace in _B82A8C0ED7C904841114FDF244F9E58E)(signal: Swift.Int32) -> () at /root/xgy_3/x-bot/.build/checkouts/swift-backtrace/Sources/Backtrace/Backtrace.swift:66 0x55ba62229549, closure #1 (Swift.Int32) -> () in static Backtrace.Backtrace.install(signals: Swift.Array) -> () at /root/xgy_3/x-bot/.build/checkouts/swift-backtrace/Sources/Backtrace/Backtrace.swift:80 0x55ba62229568, @objc closure #1 (Swift.Int32) -> ()...
This allows customizing the printed backtrace format, and separates backtrace formatting (platform agnostic) and printing (platform specific). The current format is now called `full` and I made a new one...
Could an "unable to protect … swift-backtrace … disabling backtracing" message come from this package via a Swift Community Apt Repository distribution of Swift? If yes, what might steps resolve...
