comparison man/trouble.texi @ 62897:6181dbed8947

(After a Crash): Mention emacs-buffer.gdb as a recovery mechanism.
author Noah Friedman <friedman@splode.com>
date Mon, 30 May 2005 10:48:33 +0000
parents 0f12295e50a4
children 1a33c4dbb62b
comparison
equal deleted inserted replaced
62896:63b25cade3fb 62897:6181dbed8947
349 349
350 When @code{recover-session} is done, the files you've chosen to 350 When @code{recover-session} is done, the files you've chosen to
351 recover are present in Emacs buffers. You should then save them. Only 351 recover are present in Emacs buffers. You should then save them. Only
352 this---saving them---updates the files themselves. 352 this---saving them---updates the files themselves.
353 353
354 As a last resort, if you had buffers with content which were not
355 associated with any files, or if the autosave was not recent enough to
356 have recorded important changes, you can use the
357 @file{etc/emacs-buffer.gdb} script with @code{gdb} to retrieve them
358 from a core dump--provided that a core dump was saved, and that the
359 emacs executable was not stripped of its debugging symbols.
360
354 @node Emergency Escape 361 @node Emergency Escape
355 @subsection Emergency Escape 362 @subsection Emergency Escape
356 363
357 Because at times there have been bugs causing Emacs to loop without 364 Because at times there have been bugs causing Emacs to loop without
358 checking @code{quit-flag}, a special feature causes Emacs to be suspended 365 checking @code{quit-flag}, a special feature causes Emacs to be suspended