[Please remove xemacs-patches from CC when replying] Hamish Macdonald <hamishm(a)lucent.com&gt; writes: Superb bug report... Since it is perfectly normal for a process to die while processing events we have to guard against after calls that process events.. I think the following simple bailout is the correct solution 2000-04-11 Jan Vroonhof <jan(a)xemacs.org&gt; * process-unix.c (unix_send_process): Guard against process MIA after Faccept_process_output. Index: process-unix.c =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs-20/src/process-unix.c,v retrieving revision 1.11.2.18 diff -u -r1.11.2.18 process-unix.c --- process-unix.c 2000/03/01 18:22:05 1.11.2.18 +++ process-unix.c 2000/04/11 10:31:19 ＠＠ -1139,6 +1139,14 ＠＠ volatile Lisp_Object vol_proc = proc; Lisp_Process *volatile p = XPROCESS (proc); + /* #### JV: layering violation? + + This function knows too much about the relation between the encodingstream + (DATA_OUTSTREAM) and te actual output stream p->output_stream. + + If encoding streams properly forwarded all calls, we could simply + use DATA_OUTSTREAM everywhere. */ + if (!SETJMP (send_process_frame)) { /* use a reasonable-sized buffer (somewhere around the size of the ＠＠ -1173,6 +1181,9 ＠＠ that may allow the program to finish doing output and read more. */ Faccept_process_output (Qnil, make_int (1), Qnil); + /* It could have *really* finished, deleting the process */ + if (NILP(p->pipe_outstream)) + return; old_sigpipe = (SIGTYPE (*) (int)) signal (SIGPIPE, send_process_trap); Lstream_flush (XLSTREAM (p->pipe_outstream));