rftrace | Rust Function Tracer
kandi X-RAY | rftrace Summary
kandi X-RAY | rftrace Summary
rftrace is a Rust library. rftrace has no bugs, it has no vulnerabilities and it has low support. However rftrace has a Non-SPDX License. You can download it from GitHub.
rftrace is a rust based function tracer. It provides both a backend, which does the actual tracing, and a frontend which write the traces to disk. The backend is designed to standalone and not interact with the system. As such it can be used to partially trace a kernel like RustyHermit though OS, interrupts, stdlib and application. Multiple threads are supported. It also works for normal Rust and C applications, though better tools exist for that usecase. Requires a recent nightly rust compiler (as of 28-6-2020).
rftrace is a rust based function tracer. It provides both a backend, which does the actual tracing, and a frontend which write the traces to disk. The backend is designed to standalone and not interact with the system. As such it can be used to partially trace a kernel like RustyHermit though OS, interrupts, stdlib and application. Multiple threads are supported. It also works for normal Rust and C applications, though better tools exist for that usecase. Requires a recent nightly rust compiler (as of 28-6-2020).
Support
Quality
Security
License
Reuse
Support
rftrace has a low active ecosystem.
It has 7 star(s) with 1 fork(s). There are 1 watchers for this library.
It had no major release in the last 6 months.
There are 1 open issues and 1 have been closed. On average issues are closed in 41 days. There are no pull requests.
It has a neutral sentiment in the developer community.
The latest version of rftrace is current.
Quality
rftrace has 0 bugs and 0 code smells.
Security
rftrace has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
rftrace code analysis shows 0 unresolved vulnerabilities.
There are 0 security hotspots that need review.
License
rftrace has a Non-SPDX License.
Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.
Reuse
rftrace releases are not available. You will need to build from source code and install.
Installation instructions, examples and code snippets are available.
It has 367 lines of code, 14 functions and 4 files.
It has low code complexity. Code complexity directly impacts maintainability of the code.
Top functions reviewed by kandi - BETA
kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of rftrace
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of rftrace
rftrace Key Features
No Key Features are available at this moment for rftrace.
rftrace Examples and Code Snippets
No Code Snippets are available at this moment for rftrace.
Community Discussions
No Community Discussions are available at this moment for rftrace.Refer to stack overflow page for discussions.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install rftrace
The build process is a bit weird, since we build a static rust library and then link against it. We need the second manifest, since it is not possible to change the library type outside of it. You can compile only static lib manually by renaming rftrace/staticlib/Cargo.nottoml to rftrace/staticlib/Cargo.toml and running cargo build --manifest-path rftrace/staticlib/Cargo.toml --target-dir target_static --features staticlib -vv.
cargo build runs build.rs::build() compiles part of the code as a native staticlib, by using the Cargo.toml in /staticlib and passing the staticlib feature to cargo build compiles the library as normal, without the staticlib feature and links the 'precompiled' static library from the previous step.
cargo build runs build.rs::build() compiles part of the code as a native staticlib, by using the Cargo.toml in /staticlib and passing the staticlib feature to cargo build compiles the library as normal, without the staticlib feature and links the 'precompiled' static library from the previous step.
Support
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page