Saving and Loading the Execution History
TotalView has support to save the current execution history at any given time to a recording file. The saved recording file can then be loaded into TotalView and all the replay options will be available to go back and forth within the time boundaries of the saved recording.
To save a recording, either select the Save button on the toolbar or the "Save Recording File …" menu item in the File menu. In addition, you can use the CLI dhistory command:
dhistory -save filename
The filename can be either a path or a simple file name, in which case it is saved into the current working directory. If no filename is specified, the recording is saved in the current working directory as replay_pid_hostname.recording.
The saved recording can be loaded into TotalView as follows:
• At startup, using the same syntax as when opening a core file:
totalview executable recording-file
TotalView recognizes the recording file for what it is and acts appropriately.
• After TotalView is running, using the dattach command with option -c:
dattach executable -c recording-file
• On the Root or Process window, by selecting "Debug Core or Replay Recording File ..." or on the Starting a Debug Session window, by selecting "A core file or replay recording file".
Performing any of the above displays the dialog for selecting the record file and application used during the recording session when the recording session was saved.
Again, TotalView recognizes it is dealing with a recording file.