3 ms·
The VB6 IDE, in the 90's, had a great feature where you could arbitrarily drag the execution point around. It was incredibly useful for basically zero iteration
by nomel 9y ago
The VB6 IDE, in the 90's, had a great feature where you could arbitrarily drag the execution point around. It was incredibly useful for basically zero iteration time for development. Add a breakpoint, step over your code, and if something went wrong, drag the execution point back a few lines, fix it, and try again.
This seems like a holy grail for IDEs. Why was this feature lost in time, or have I been using the wrong IDEs?
- taspeotis 9y agohttps://docs.microsoft.com/en-gb/visualstudio/debugger/navigating-through-code-with-the-debugger#BKMK_Set_the_next_statement_to_execute https://docs.microsoft.com/en-gb/visualstudio/debugger/navig...
- mlevental 9y agohow is this different from just setting an earlier breakpoint? what does dragging matter other than us?
- maxxxxx 9y agoIn C# and visual studio you can do it. I think C++ also has edit and continue in VS.
- nly 9y agoThis is called 'reversible debugging'. It's not lost. GDB can do this[0] and there are commercial products on the market that can do it better[1] [0] https://www.gnu.org/software/gdb/news/reversible.html https://www.gnu.org/software/gdb/news/reversible.html [1] https://undo.io/products/undodb/ https://undo.io/products/undodb/
- ahartmetz 9y agoThere is also a free product that can do it better http://rr-project.org/ http://rr-project.org/
- robertkrahn01 9y agoLive Debugging in Smalltalk https://www.youtube.com/watch?v=1kuoS796vNw https://www.youtube.com/watch?v=1kuoS796vNw
- GordonS 9y agoI think one of the recent Visual Studio 2017 updates added this. I think they called it'time travel debugging'