In article <[EMAIL PROTECTED]>, David Kastrup <[EMAIL PROTECTED]> writes:
> Hi, recently (as in starting at most a few weeks ago, if I am > correctly), I frequently have the following crash after suspending my > computer, wakening it up again, starting gnus, forgetting to answer a > password prompt for a few minutes and then finally answering it. Ok, > I am aware that this is not a reproducible recipe. So I ran Emacs > under the debugger for the next time this might happen. Here is the > backtrace: > If Emacs crashed, and you have the Emacs process in the gdb debugger, > please include the output from the following gdb commands: > `bt full' and `xbacktrace'. > If you would like to further debug the crash, please read the file > /usr/local/emacs-21/share/emacs/22.0.94/etc/DEBUG for instructions. > frame 0 > #0 0x0818fe0f in send_process_object (proc=158730484, start=155210699, > end=137476297) at /home/tmp/emacs/src/process.c:5699 > 5699 if (! EQ (coding->symbol, p->encode_coding_system)) > (gdb) p coding > $1 = (struct coding_system *) 0x0 Although I can't reproduce that bug, I found the code I committed recently was incomplete. As I've just installed a fix, could you please try again. --- Kenichi Handa [EMAIL PROTECTED] _______________________________________________ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug