Search Results for "backtrace"

This is a Rust crate that provides a convenient derive macro (#[derive(Error)]) for implementing std::error::Error on your custom error types (structs or enums). The goal is to enable library authors to build expressive, typed error types, with readable Display implementations (via #[error("...")] annotations) as well as From conversions (#[from]), source tracking (#[source]), and optionally backtraces. It is designed so that switching from handwritten error implementation to using this...

This is a Rust library (crate) that provides a flexible, concrete error type built atop the standard std::error::Error trait. Its primary goal is to make error handling in applications easy: instead of defining lots of custom error types, you can use anyhow::Error (or the alias anyhow::Result<T>) for fallible functions. The crate supports attaching context to errors, so you can convert a low-level error (like “file not found”) into one with richer diagnostics (“Failed to read instructions...

Backtrace is a drop-in replacement for libexecinfo's and glibc's backtrace API. Since libexecinfo didn't work on OpenBSD and glibc's backtrace is pure linux goo it was decided to write a working replacement.

Provides interface for generating stack traces from within a program. Inspired by Java's ability to do a backtrace whenever an error occurs, this provides similar capability in C/C++. Very lightweight and portable, where available builds on execinfo.h.