RE: [FYI] tutorial for process record and reverse debugging

["Jakob Engblom" <jakob at virtutech dot com>]

> 
> Seems to me that if you're replaying, and you reach the end of the
> recorded log, at least one natural thing to do is to stop.  Could be
> that another natural thing to do would be to automatically switch
> from replay mode to record mode and keep going -- but I'm not sure
> if I could safely assume that that was the user's desire.
> 
> Sounds like a case for a query, and/or a user-settable mode.

Unless the backend tool is one that silently goes on recording here, like I know
Simics does and I presume any other simulation-based solution will. And
VMWare-style virtual-machine-based solutions.  So a query for how a target
behaves would  be nice. 

In our experience, going on recording seems to be the natural thing to do.  You
can look at this way: the end of recording is nothing a user knows about, as the
extent of the recording in time is a tool implementation aspect. As far as the
user is concerned, the program is being reversed and run forward, without much
care for how far into the execution they have gotten at any particular point in
user time.  If you want to execute for a bounded amount, use a "continue N
cycles"-style command (which gdb does not have either). 

/jakob