-
Notifications
You must be signed in to change notification settings - Fork 394
fuzz, capture: split up protobuf dumping and capture ctx #8129
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
Conversation
Performance Measurements ⏳
|
35cbc12 to
278d2a5
Compare
Performance Measurements ⏳
|
2f99af3 to
278d2a5
Compare
Performance Measurements ⏳
|
8143899 to
278d2a5
Compare
Performance Measurements ⏳
|
| void | ||
| fd_dump_vm_syscall_to_protobuf( fd_vm_t const * vm, | ||
| char const * fn_name ) { | ||
| char const * syscall_name_filter = vm->instr_ctx->runtime->log.dump_proto_ctx->dump_syscall_name_filter; |
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.
a cleaner way to do this to avoid a strcmp for every syscall is to map the syscall function pointers to the syscall names so all you have to do is a pointer comparison
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.
theres no current map that does this, and this would also need to be maintained separately every time a new syscall is added, so i think the current implementation should be fine for now
278d2a5 to
1e08dc1
Compare
Performance Measurements ⏳
|
ibhatt-jumptrading
left a comment
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.
don't love the function name strcmp but not blocking
No description provided.