Re:All my favorite tracing tools: eBPF, QEMU, Perfetto, new ...
by inetknght on Wednesday December 06, 2023 @05:01PM
(#38550134)
I've seen undo.io several times at cppcon. I've been throughly impressed with the demonstrations at the conference and came to this thread specifically to recommend undo.io. I was particularly impressed this year by a demonstration of debugging stack smashing -- that's something I recently worked around stack smashing in protobuf which happens before `main()` even starts. It seems perfect for undo.io to help debug :)
I'm still waiting on the keyserver to be able to run in Kubernetes though
Re:All my favorite tracing tools: eBPF, QEMU, Perfetto, new ...
by mark_undoio on Thursday December 07, 2023 @09:37AM
(#38556789)
> I was particularly impressed this year by a demonstration of debugging stack smashing
I'm glad you liked it - and that's useful feedback for other demos we give!
> I'm still waiting on the keyserver to be able to run in Kubernetes though
I believe support for that is on the way. If you're already in touch then I imagine you'll get an announcement soon.
I just read your post and don't think it would take much to integrate with some of the visualisations you posted about, as a first step.
We've played around in the past with a sampling profiler (code here, requires a copy of our product to be useful though it could easily port to rr): https://github.com/undoio/addons/tree/master/sample_function... which can output in a format understood by Brendan Gregg's flame frames (https://www.brendangregg.com/flamegraphs.html)
But that's not quite the kind of tracing you're talking about. We also built a printf-style interface to our recording files, which seems closer: https://docs.undo.io/PostFailureLogging.html
Something like that but outputting trace events that can be consumed by Perfetto (say) would not be so hard to add. If we considered modifying the core record/replay engine then even more powerful things become possible.