diff options
author | Hui Zhu <teawater@gmail.com> | 2008-10-23 03:05:41 +0000 |
---|---|---|
committer | Hui Zhu <teawater@gmail.com> | 2008-10-23 03:05:41 +0000 |
commit | cb7f0c8fa77484873c188c5b9c8956f846bcc430 (patch) | |
tree | e4ca89ebb47e98814c73646aa34f7aa77e86d0fe /gdb | |
parent | 744abaa92ca8c97bd3577cc709c7142bb20f284a (diff) | |
download | gdb-cb7f0c8fa77484873c188c5b9c8956f846bcc430.tar.gz |
2008-10-22 Hui Zhu <teawater@gmail.com>
* gdb.texinfo: Add documentation for process record and replay.
Diffstat (limited to 'gdb')
-rw-r--r-- | gdb/doc/ChangeLog | 4 | ||||
-rw-r--r-- | gdb/doc/gdb.texinfo | 97 |
2 files changed, 101 insertions, 0 deletions
diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index df078117066..03448c80fd1 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,3 +1,7 @@ +2008-10-22 Hui Zhu <teawater@gmail.com> + + * gdb.texinfo: Add documentation for process record and replay. + 2008-10-10 Michael Snyder <msnyder@vmware.com> * gdb.texinfo: Document the 'bc' and 'bs' (reverse) commands, diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index 60c4105f03f..65d65e625e3 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -144,6 +144,7 @@ software in general. We will miss him. * Running:: Running programs under @value{GDBN} * Stopping:: Stopping and continuing * Reverse Execution:: Running programs backward +* Process record and replay:: Recording programs running message and replay it * Stack:: Examining the stack * Source:: Examining source files * Data:: Examining data @@ -4963,6 +4964,102 @@ This is the default. @end table +@node Process record and replay +@chapter Recording programs running message and replay it +@cindex process record and replay +@cindex recording programs running message and replay it + +In a architecture environment that supports process record and replay, +process record and replay target can record a log of the process execution, +and replay it with both forward and reverse execute commands. + +When this target is in use, if the execution log includes the record for +the next instruction, @value{GDBN} will debug in replay mode. So inferior +will not really execute and all the execution events are taken from the +execution log. Just the values of registers (include pc register) and +memory of the inferior will be changed. + +Otherwise, @value{GDBN} will debug in record mode. So inferior will +execute normally and @value{GDBN} will record the execution log. + +If you are debugging in a architecture environment that supports +process record and replay, @value{GDBN} provides the following commands. + +@table @code +@kindex target record +@kindex record +@kindex rec +@item target record +This a standard command to start process record and replay target. +Process record and replay target can only debug a process that already +running. Therefore you need to first start the process @code{run}, +and then start the recording @code{record}. + +@kindex stoprecord +@kindex sr +@item stoprecord +Stop process record and replay target at once. When Process record and +replay target stops, all the execution log will be deleted and the inferior +will either be terminated, or remain in its final state. + +When you stop the process record and replay target in record mode (at the +end of the execution log), the inferior will be stopped at the next +instruction that would have been recorded. In other words, if you record +for a while and then stop recording, the inferior process will be left in +the same state as if recording never happened. + +On the other hand, if the process record and replay target is stopped while +in replay mode (that is, not at the end of the execution log but at some +earlier point), the inferior process will become ``live'' at that earlier state, +and it will then be possible to continue debugging the process ``live'' from +that state. + +When the inferior process exits, or @value{GDBN} detaches from it, process +record and replay target will automatically stop itself. + +@kindex set record-insn-number-max +@item set record-insn-number-max @var{limit} +Set the limit of instructions to be recorded. Default value is 200000. + +In this case, if record instructions number is bigger than @var{limit}, +@value{GDBN} will auto delete the earliest recorded instruction execute +log. + +If set to 0, @value{GDBN} will not delete the earliest recorded instruction +execute log. Record instructions number limit function will disable. + +@kindex show record-insn-number-max +@item show record-insn-number-max +Show the value of recorded instructions limit. + +@kindex set record-stop-at-limit +@item set record-stop-at-limit on +Set the behavior when record instructions limit is reached. +This is the default mode. Meaning that @value{GDBN} will stop ask user +want close @code{record-stop-at-limit} or stop inferior. + +@item set record-stop-at-limit off +This mean that @value{GDBN} will auto delete the oldest record to make +room for each new one. + +@kindex show record-stop-at-limit +@item show record-stop-at-limit +Show the value of record-stop-at-limit. + +@kindex info record-insn-number +@item info record-insn-number +Show the current number of recorded instructions. + +@kindex delrecord +@kindex dr +@item delrecord +When record target running in replay mode (``in the past''), delete the +subsequent execution log and begin to record a new execution log starting +from the current address. It means you will abandon the previously +recorded ``future'' and begin recording a new ``future''. +@end table + + @node Stack @chapter Examining the Stack |