On Nov 27, 2012, at 4:54 PM, Sean Kelly <[email protected]> wrote:
> On Nov 11, 2012, at 4:41 AM, Leandro Lucarella <[email protected]> wrote: > >> David Held, el 9 de November a las 22:41 me escribiste: >>> >>> Finally, what the debugger cannot do is provide you with a history >>> of what happened, except insofar as you are willing to manually >>> capture the state change of various memory locations as you step >>> through the program. >> >> Well, then I guess you don't know gdb's reverse debugging :D >> http://sourceware.org/gdb/news/reversible.html > > The first demo I saw of this was the Asymetrix C++ debugger back in the mid > 90s. A pretty cool idea, though I've never actually felt I needed it. I've done a lot of monte carlo based stuff where an it could take an hour to reproduce a problem. I've wanted to go backwards once I captured a bug, but have never had the luxury of being able to do that. _______________________________________________ dmd-internals mailing list [email protected] http://lists.puremagic.com/mailman/listinfo/dmd-internals
