Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add option to export to CSV #135

Open
tmplt opened this issue Jan 20, 2022 · 2 comments
Open

Add option to export to CSV #135

tmplt opened this issue Jan 20, 2022 · 2 comments
Labels
enhancement New feature or request
Milestone
v0.4.0

Comments

@tmplt
Copy link
Member

tmplt commented Jan 20, 2022

Some --export-csv flag should be added to that the resolved trace can easily be piped into whatever post-processing program one can come up with. The CSV will have to be exhaustive.
@tmplt tmplt added the enhancement New feature or request label Jan 20, 2022
@tmplt tmplt added this to the v0.4.0 milestone Jan 20, 2022
@tmplt
Copy link
Member Author

tmplt commented Jan 20, 2022

All echoes that aren't CSV will have to be done to stderr.

@tmplt
Copy link
Member Author

tmplt commented Jan 20, 2022 •
edited
Loading

Some thoughts:

  • should we just drop the messy frontend implementation is favor of simply talking CSV? Doing so would increase modularity and decrease complexity and code that need to be supported. Then some choice post-processing scripts could be maintained as a starting point.

  • cargo itm-scope [trace --recovery-flavor [ rtic | zephyr | ... ] | replay ... ] [--out trace.csv]?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
v0.4.0
Development

No branches or pull requests
1 participant
@tmplt