-
Notifications
You must be signed in to change notification settings - Fork 346
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
Visualize .orbit output data in case of CLI version #4817
Comments
That should be pretty straightforward to archive. I do see two possible ways:
|
Thanks, I'll give a try to point 2 (python) first. |
This python stuff works, and it's possible to print out all the captured events. But now it seems that
It finds debug info successfully, profiles for 10 seconds, saves the trace and exits. When I'm loading this trace into Orbit GUI - it's shows nothing. When I'm analizing it with python scripts - no events mentioning any functions. I plan to debug it somehow and would appreciate any ideas about what could be the reason. |
Fixed by #4818 |
Thanks for the fix. Hope that it works now on your side! |
Yes, it seems to be working. At least now I'm able to "Load capture" with a .orbit file generated by OrbitClientGgp, and it looks exactly like the capture produced by the gui version. |
I'd like to know if there is a way to somehow get human readable data from
.orbit
(in my case it'shello_2023_03_09_14_00_13.orbit
) output file. I'm usingWITH_GUI=OFF
version.The text was updated successfully, but these errors were encountered: