-
Notifications
You must be signed in to change notification settings - Fork 433
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(cli): tracer #1188
feat(cli): tracer #1188
Conversation
cli/src/commands/trace.rs
Outdated
)] | ||
pub struct TraceCmd { | ||
#[arg(short, long, default_value_t = 30)] | ||
/// Include the "top" number of functions |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: a bit unusual to have the comment under the macro
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
also usually attribute comments have periods at end throughput repo
} | ||
} | ||
|
||
fn _build_radare2_lookups( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can delete?
Added a RISC-V tracer command to the
cargo prove
CLI that will allow users to trace which functions are expensive.Usage:
TRACE_FILE
environment variable set to a file name, when executing the ELF (with inputs) to save a trace of thepc
to the specified filecargo prove trace -- --elf path_to_elf --trace trace_file
to output a trace of function calls