[Feature Request] Step backwards in debugger

815 views
Skip to first unread message

Dan Cancro

unread,
Sep 6, 2017, 4:36:02 PM9/6/17
to Google Chrome Developer Tools
During an execution pause, this feature would allow you to travel backwards through previously executed lines of code in developer tools. Of course it would not undo the execution of those lines but it would allow you to know what they were. It would keep a history of executed lines of a configurable length, but it probably doesn't need to be that long.

This would be VERY handy in debugging. You just set it pause on exceptions and then when an exception is thrown and it pauses, you simply step backwards through the executed lines until you find an interesting one. You can then add a breakpoint there, rerun the page, and inspect the stack until you solve the problem.


Blaise Bruer

unread,
Sep 6, 2017, 6:06:50 PM9/6/17
to Google Chrome Developer Tools
This is still an area of research and people are still writing many papers on the subject. Microsoft has been experimenting with the idea as seen here: https://blogs.windows.com/msedgehttp://rr-project.org/dev/context/time-travel-debugging/

Mozilla has been playing around with the idea as well like here: http://rr-project.org/

As of now we don't have any immediate plans on doing this, but it is something that we talk about on the team frequently and are keeping tabs on what research has been showing.

Thanks for the request though!

On Wed, Sep 6, 2017 at 1:36 PM Dan Cancro <dan.c...@gmail.com> wrote:
During an execution pause, this feature would allow you to travel backwards through previously executed lines of code in developer tools. Of course it would not undo the execution of those lines but it would allow you to know what they were. It would keep a history of executed lines of a configurable length, but it probably doesn't need to be that long.

This would be VERY handy in debugging. You just set it pause on exceptions and then when an exception is thrown and it pauses, you simply step backwards through the executed lines until you find an interesting one. You can then add a breakpoint there, rerun the page, and inspect the stack until you solve the problem.


--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/a0325fb6-befc-4415-9c47-a242f2f84ccd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Eyal Herlin

unread,
Jul 27, 2018, 7:18:22 AM7/27/18
to Chrome DevTools
This feature seems to have just landed in Firefox nightly: https://twitter.com/jasonlaster11/status/1022547128818782208
Any updates on the status of this on Chrome?


On Thursday, September 7, 2017 at 1:06:50 AM UTC+3, Blaise Bruer wrote:
This is still an area of research and people are still writing many papers on the subject. Microsoft has been experimenting with the idea as seen here: https://blogs.windows.com/msedgehttp://rr-project.org/dev/context/time-travel-debugging/

Mozilla has been playing around with the idea as well like here: http://rr-project.org/

As of now we don't have any immediate plans on doing this, but it is something that we talk about on the team frequently and are keeping tabs on what research has been showing.

Thanks for the request though!

On Wed, Sep 6, 2017 at 1:36 PM Dan Cancro <dan.c...@gmail.com> wrote:
During an execution pause, this feature would allow you to travel backwards through previously executed lines of code in developer tools. Of course it would not undo the execution of those lines but it would allow you to know what they were. It would keep a history of executed lines of a configurable length, but it probably doesn't need to be that long.

This would be VERY handy in debugging. You just set it pause on exceptions and then when an exception is thrown and it pauses, you simply step backwards through the executed lines until you find an interesting one. You can then add a breakpoint there, rerun the page, and inspect the stack until you solve the problem.


--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-developer-tools+unsub...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages