4 ms·

Thanks very much for posting this article. I found it very intriguing. I read it carefully but I didn’t visit all the links or watch all of the in-line videos.

Thanks very much for posting this article. I found it very intriguing. I read it carefully but I didn’t visit all the links or watch all of the in-line videos. I would say that for the most part I am a printf-style debugger. I remember reading some years ago (on HN, I believe) about time travel debugging in - I believe - C# and I was really impressed but I don’t code in C# so it soon left my mind. I have a deep appreciation for mastering one’s toolset. I can’t think of the number of times that I learned something new about a tool (language, editor, shell, browser, whatever) that I use daily that changes my workflow - it has happened so many times. And as with all things code, sometimes new features are added. I am going to try to make a point to re-read this article later and to visit each link and glean what I can. I mostly code in Go. I wonder, does anybody know how much of this stuff might be supported there?

mark_undoio 4y ago
For time travel debugging in Go: The Delve debugger for Go supports debugging rr traces: https://github.com/go-delve/delve/blob/master/Documentation/usage/dlv_replay.md https://github.com/go-delve/delve/blob/master/Documentation/... Undo (who I work for) maintain a fork that debugs our LiveRecorder recordings: https://docs.undo.io/GoDelve.html https://docs.undo.io/GoDelve.html Either rr (https://rr-project.org/ https://rr-project.org/) or our UDB debugger (https://undo.io/solutions/products/udb/ https://undo.io/solutions/products/udb/) can do some time travel debugging of Go programs via GDB's built-in support for Go. I believe its weakness is in support for goroutines, since they don't map well onto its idea of how programs run.
- pcdevils 4y ago
  The same tools don't work on windows either. Delve works well as a remote debugger against go on windows server though. Another fun one is go won't create dumps on panic on windows when GOTRACEBACK=crash is set.
intelVISA 4y ago
Not tried it unfortunately but there's a travel-time debugger for C(++) somewhere.

mark_undoio 4y ago

For time travel debugging in Go: The Delve debugger for Go supports debugging rr traces: https://github.com/go-delve/delve/blob/master/Documentation/usage/dlv_replay.md https://github.com/go-delve/delve/blob/master/Documentation/... Undo (who I work for) maintain a fork that debugs our LiveRecorder recordings: https://docs.undo.io/GoDelve.html https://docs.undo.io/GoDelve.html Either rr (https://rr-project.org/ https://rr-project.org/) or our UDB debugger (https://undo.io/solutions/products/udb/ https://undo.io/solutions/products/udb/) can do some time travel debugging of Go programs via GDB's built-in support for Go. I believe its weakness is in support for goroutines, since they don't map well onto its idea of how programs run.

pcdevils 4y ago
The same tools don't work on windows either. Delve works well as a remote debugger against go on windows server though. Another fun one is go won't create dumps on panic on windows when GOTRACEBACK=crash is set.

intelVISA 4y ago

Not tried it unfortunately but there's a travel-time debugger for C(++) somewhere.