ccaa2e5f1d
Summary: Release notes: https://blog.rust-lang.org/2023/10/05/Rust-1.73.0.html This release is coupled with an update of the `anyhow` and `thiserror` crates because the unstable standard library API for backtraces has changed. Fbcode changes: - `feature(default_free_fn)` deleted (D50300881) - `noop_method_call` lint becomes warn-by-default (D50486032, D50516201) - stronger `invalid_reference_casting` detection (D50488164) - `feature(unix_chown)` has been stabilized - `feature(provide_any)` and `std::provider` deleted - `clippy::unwrap_or_else_default` renamed to `clippy::unwrap_or_default` - type inference ambiguities (D51780425) - `nu-command` build error (D51779062) Reviewed By: AndreasBackx, shayne-fletcher Differential Revision: D50294321 fbshipit-source-id: 0fac87f6ba072ad029f9ce41ce94ed813e855b20 |
||
|---|---|---|
| .. | ||
| src | ||
| Cargo.toml | ||
| README.md | ||
A safe ptrace interface
This crate provides a safe and Rustic alternative to the infamous ptrace API.
There are many extremely subtle aspects of the raw ptrace API and this crate
helps avoid common pitfalls.
Note that this library is still rather low-level and does not claim to solve all your ptrace problems. You have been warned!
Features
- Ergonomic interface that provides a state machine for ptrace states. This
avoids the infamous
ESRCHerrors that can happen when you use the ptrace API incorrectly. - Provides an interface to read/write guest's memory (see "memory" feature flag).
- Provides an optional and semi-experimental async interface, which can be used
with
tokio(see "notifier" feature).
Usage
Add this to your Cargo.toml file:
safeptrace = "0.1"
Feature Flags
"memory" (off by default)
Provides access to the guest's memory. Memory can only be safely accessed when
the guest is in a stopped state, thus the MemoryAccess trait is only
implemented for the Stopped type.
"notifier" (off by default)
Provides an async interface for ptrace using notifier threads. This is semi-experimental, but testing shows that it has very good performance. It works by spawning a separate thread for each thread being traced, waiting for ptrace events in a loop. Thus, there will be 1 thread per guest thread.
Use with:
safeptrace = { version = "0.1", features = ["async"] }