| tag | 5ae928af43ad8c85e079a837b6e3f3fe474d1c51 | |
|---|---|---|
| tagger | Alex Crichton <alex@alexcrichton.com> | Wed Oct 11 17:37:42 2017 -0700 |
| object | 9cfc4b51dd76ff89791736e765e7d3df3fae9a23 |
Version 0.1.15
| commit | 9cfc4b51dd76ff89791736e765e7d3df3fae9a23 | [log] [tgz] |
|---|---|---|
| author | Alex Crichton <alex@alexcrichton.com> | Wed Oct 11 17:37:25 2017 -0700 |
| committer | Alex Crichton <alex@alexcrichton.com> | Wed Oct 11 17:37:31 2017 -0700 |
| tree | 64b21bff78dee6e92fae5eab053055faed0b8c20 | |
| parent | eabc392b91ba9d56da21a50eb53773038eecec69 [diff] |
Bump backtrace-sys to 0.1.15
A library for acquiring backtraces at runtime for Rust. This library aims to enhance the support given by the standard library at std::rt by providing a more stable and programmatic interface.
[dependencies] backtrace = "0.3"
extern crate backtrace;
Note that this crate requires make, objcopy, and ar to be present on Linux systems.
To simply capture a backtrace and defer dealing with it until a later time, you can use the top-level Backtrace type.
extern crate backtrace; use backtrace::Backtrace; fn main() { let bt = Backtrace::new(); // do_some_work(); println!("{:?}", bt); }
If, however, you'd like more raw access to the actual tracing functionality, you can use the trace and resolve functions directly.
extern crate backtrace; fn main() { backtrace::trace(|frame| { let ip = frame.ip(); let symbol_address = frame.symbol_address(); // Resolve this instruction pointer to a symbol name backtrace::resolve(ip, |symbol| { if let Some(name) = symbol.name() { // ... } if let Some(filename) = symbol.filename() { // ... } }); true // keep going to the next frame }); }
This library currently supports OSX, Linux, and Windows. Support for other platforms is always welcome!
backtrace-rs is primarily distributed under the terms of both the MIT license and the Apache License (Version 2.0), with portions covered by various BSD-like licenses.
See LICENSE-APACHE, and LICENSE-MIT for details.