Question 1

How do I install and run lockbud on my Rust project?

Accepted Answer

Clone the repository, install with the specified Rust nightly using cargo install, then run cargo lockbud in your project directory after cleaning with cargo clean. Use flags like -k to select detectors, as detailed in the example section.

Question 2

Lockbud vs cargo clippy for deadlock detection?

Accepted Answer

Lockbud is specialized for concurrency and memory bugs based on academic research, while Clippy is a general linter. Lockbud may catch more subtle deadlock patterns, but Clippy is more integrated and has fewer false positives for general code style issues.

Question 3

Does lockbud work with async Rust or Tokio?

Accepted Answer

The README doesn't mention async support, and it only lists std::sync, parking_lot, and spin for locks. Tokio's synchronization primitives are likely not supported, limiting its use in async-heavy codebases.

Question 4

How can I reduce false positives when using lockbud?

Accepted Answer

Use the -l flag to blacklist dependency crates that cause false positives, such as cc, and focus on your project code. The deadlock detectors are more reliable than memory or panic detectors, per the announcements.

Question 5

Can lockbud detect use-after-free in unsafe code?

Accepted Answer

Yes, it includes a memory bug detector for use-after-free and invalid-free, but the README warns of high false positives from dependencies, so results should be interpreted cautiously with crate filtering.

Question 6

Is lockbud compatible with stable Rust?

Accepted Answer

No, it currently requires a specific Rust nightly version (e.g., nightly-2025-10-02), as stated in the install section, making it unsuitable for projects locked to stable releases.

lockbud

What is lockbud?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions