(ddd.info)Saving Sessions

---

Next: Resuming Sessions Up: Sessions

---

Enter node , (file) or (file)node

2.3.1 Saving Sessions
---------------------

To save a session, select `File => Save Session As'.  You will be asked
for a symbolic session name SESSION.

   If your program is running (Note: Running), or if you have opened a
core file (Note: Opening Core Dumps), DDD can also include a core
file in the session such that the debuggee data will be restored when
re-opening it.  To get a core file, DDD typically must "kill" the
debuggee.  This means that you cannot resume program execution after
saving a session.  Depending on your architecture, other options for
getting a core file may also be available.

   Including a core dump is necessary for restoring memory contents and
the current execution position.  To include a core dump, enable
`Include Core Dump'.

   After clicking on `Save', the session is saved in
`~/.ddd/sessions/SESSION'.

   Here's a list of the items whose state is saved in a session:
   * The state of the debugged program, as a core file.(1)

   * All breakpoints and watchpoints (Note: Stopping).

   * All signal settings (Note: Signals).

   * All displays (Note: Displaying Values).(2)

   * All DDD options (Note: Saving Options).

   * All debugger settings (Note: Debugger Settings).

   * All user-defined buttons (Note: Defining Buttons).

   * All user-defined commands (Note: Defining Commands).

   * The positions and sizes of DDD windows.

   * The command history (Note: Command History).

   After saving the current state as a session, the session becomes
"active".  This means that DDD state will be saved as session defaults:

   * User options will be saved in `~/.ddd/sessions/SESSION/init'
     instead of `~/.ddd/init'.  Note: Saving Options, for details.

   * The DDD command history will be saved in
     `~/.ddd/sessions/SESSION/history' instead of `~/.ddd/history'.
     Note: Command History, for details.

   To make the current session inactive, open the _default session_
named `[None]'.  Note: Resuming Sessions, for details on opening
sessions.

   ---------- Footnotes ----------

   (1) Only if a core file is included.

   (2) If a core file is _not_ to be included in the session, DDD data
displays are saved as _deferred_; that is, they will be restored as
soon as program execution reaches the scope in which they were created.
Note: Creating Single Displays, for details.