Time-Travel Debugging for JavaScript/Node.js
microsoft.com
Time-Travel Debugging for JavaScript/Node.js
1–10 of 12 posts
Re: Time-Travel Debugging for JavaScript/Node.js
#2Re: Time-Travel Debugging for JavaScript/Node.js
#3But these tools were internal and not available outside.It did require good assembly knowledge and always condidered cool by everyone else because not everyone knew or mastered it.I always thought that Microsoft should open source or at least release it outside .
Re: Time-Travel Debugging for JavaScript/Node.js
#4Re: Time-Travel Debugging for JavaScript/Node.js
#5September 2016
Re: Time-Travel Debugging for JavaScript/Node.js
#6If anyone knows if such a feature will be available with Node / V8 in the future as well, please do tell.
Re: Time-Travel Debugging for JavaScript/Node.js
#7When I was working at Microsoft ,we used Time travel tracing extensively to find out bugs in asp.net,IIS and many other server side technologies where you cannot debug live.You can capture the trace from the live process while reproducing the isuue.Move it your local machine and debug yourself to oblivion :) .Imagine you use gdb/windbg and you can go back or forth from any breakpoints ,check the state of stack ,any v…
Or a commercial, more polished product http://undo.io/
Other environments, like JVM also have such tools (e.g. http://chrononsystems.com/).
Re: Time-Travel Debugging for JavaScript/Node.js
#8When I was working at Microsoft ,we used Time travel tracing extensively to find out bugs in asp.net,IIS and many other server side technologies where you cannot debug live.You can capture the trace from the live process while reproducing the isuue.Move it your local machine and debug yourself to oblivion :) .Imagine you use gdb/windbg and you can go back or forth from any breakpoints ,check the state of stack ,any v…