(After a Crash): Describe how to use emacs-buffer.gdb more explicitly.

1 files changed, 16 insertions, 3 deletions

diff --git a/man/trouble.texi b/man/trouble.texi
index 2c81592679..ff846821ff 100644
--- a/man/trouble.texi
+++ b/man/trouble.texi
@@ -351,12 +351,25 @@ visits the file but gets the text from the auto-save file.
 recover are present in Emacs buffers.  You should then save them.  Only
 this---saving them---updates the files themselves.
 
+
   As a last resort, if you had buffers with content which were not
 associated with any files, or if the autosave was not recent enough to
 have recorded important changes, you can use the
-@file{etc/emacs-buffer.gdb} script with @code{gdb} to retrieve them
-from a core dump--provided that a core dump was saved, and that the
-emacs executable was not stripped of its debugging symbols.
+@file{etc/emacs-buffer.gdb} script with GDB (the GNU Debugger) to
+retrieve them from a core dump--provided that a core dump was saved,
+and that the Emacs executable was not stripped of its debugging
+symbols.
+
+  To use this script, run @code{gdb} with the file name of your
+Emacs executable and the file name of the core dump, e.g. @samp{gdb
+/usr/bin/emacs core.emacs}.  At the @code{(gdb)} prompt, load the
+recovery script: @samp{source /usr/src/emacs/etc/emacs-buffer.gdb}.
+You can now use the commands @code{ybuffer-list} and
+@code{ysave-buffer} to list and save buffers.  The @code{ysave-buffer}
+command takes a buffer number (as listed by @code{ybuffer-list}) and a
+file name to which to write the buffer contents.  You should use a
+file name which does not already exist; no backups of the previous
+contents of the file will be saved, if any.
 
 @node Emergency Escape
 @subsection Emergency Escape