FireDBG.for.Rust
console
FireDBG.for.Rust | console | |
---|---|---|
2 | 20 | |
1,166 | 3,196 | |
3.2% | 3.2% | |
8.7 | 8.5 | |
19 days ago | 5 days ago | |
Rust | Rust | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
FireDBG.for.Rust
- Time Travel Visual Debugger for Rust
-
Show HN: FireDBG – A Time Travel Visual Debugger for Rust
Seems to be dual MIT and Apache 2, although the "license in every subdirectory" makes it (a) not show up in the GitHub license detector (b) presumably places the burden upon the user to only use code from each directory or something https://github.com/SeaQL/FireDBG.for.Rust#license
console
-
Rust Tooling: 8 tools that will increase your productivity
tokio-console is a debugger for Rust async programs that use Tokio. To get started, add the console-subscriber crate to your project and add the following line which will initialise the subscriber and allow tokio-console to connect to it:
-
How to detect lock contention in rust?
You could try https://github.com/tokio-rs/console to debug and profile what happens with tokio tasks in your program.
-
Using Rust at a startup: A cautionary tale
The tokio-console CLI is a fun one. The console-subscriber supports shipping to a console server running elsewhere, apparently. That gives you a window into what's happening now.
-
Hey Rustaceans! Got a question? Ask here! (42/2022)!
Tokio console maybe? https://github.com/tokio-rs/console
-
use both of tracing-subscriber and tokio-soncole
If I add "console_subscriber::init()" line as https://github.com/tokio-rs/console recommends, tracing_subscriber cannot be initialized.
-
Any recommendations for profiling High performance rust code?
I'm building an HTTP load tester called pdc! I have run out of obvious (to me at least) places to look for performance gains. I'm achieving around 45,000 requests per second, per core. Right now I'm using hyper with a separate tokio runtime (in current thread mode) running on each core. So far having runtime on each core/NUMA node has really helped with cache coherency. Any recommendations for profiling beyond tokio console or tokio metrics (Convenient timing amirite!)?
-
Announcing `tracing` 0.1.30 with experimental `valuable`support!
It was just an accident and has been fixed https://github.com/tokio-rs/console/issues/270.
-
[Question] Is Tokio a poor fit for non-network related concurrent applications?
P.S. Tokio [now also has Tokio Console](https://github.com/tokio-rs/console) allowing you to conveniently troubleshoot your tasks if they are causing issues :)
-
How do I profile a Rust web application in production?
You can opt-in to async runtime such as tokio, and you can use tokio-rs/console for it's top-like metric
- `tokio::spawn` to handle `actix` message doesn't wait?
What are some alternatives?
vscode-lldb - A native debugger extension for VSCode based on LLDB [Moved to: https://github.com/vadimcn/codelldb]
mirage - MirageOS is a library operating system that constructs unikernels
tracing - Application level tracing for Rust.
loom - Concurrency permutation testing tool for Rust.
prost - PROST! a Protocol Buffers implementation for the Rust Language
evcxr
delve - Delve is a debugger for the Go programming language.
pdc
ferros - A Rust-based userland which also adds compile-time assurances to seL4 development.
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
crusty-core - A small library for building fast and highly customizable web crawlers
pprof - pprof is a tool for visualization and analysis of profiling data