Hacker News new | ask | show | jobs
by Veserv 391 days ago
This is just a trace viewer. Except the trace visualization is vastly less dense than any standard trace viewer and seems to provide no meaningful execution time information.

Compare to chrome://tracing

https://www.chromium.org/developers/how-tos/trace-event-prof...

I am not sure if trace visualizers were invented 20 years ago for the original time travel debuggers, but they have certainly been used for time travel debugging visualization since at least 20 years ago.
1 comments
sureglymop 391 days ago
It's definitely a little more than just a trace viewer.

As the page reads, it is a time traveling debugger. You can jump back and forth between different snapshots of time during the execution of your program. It's neat because for compiled languages like rust doing something like this is more advanced.

link
Veserv 391 days ago
That is exactly how trace viewers have been used with time travel debuggers for literally, and I do mean literally, over 20 years.

You click a point in the trace, you jump to that point in time. That has been the standard integration for decades.

link
sureglymop 391 days ago
I was under the impression that with a trace viewer you would do that after the execution of the program has finished. Learned something!
link
quotemstr 391 days ago
It's both. It is a trace viewer, but they instrument native code to emit logs of its operation, e.g. calls and returns, similar to what the recent non-performance-counter rr branch does. Except for some reason it's coupled to a specific GUI and a specific language instead of being a general purpose tool like RR is.

The tech industry is getting stupider and hype-ier as it implodes.

link