>>>> "SY" == Steve Youngs
<youngs(a)xemacs.org> writes:
SY> |--==> "MS" == Michael Sperber
<sperber(a)informatik.uni-tuebingen.de> writes:
MS> The patch I sent to -beta or the (slightly extended) one I sent to
MS> -patches?
SY> Just checked the patch sent to -patches... nope, sorry, it doesn't fix
SY> the problem. But it's definitely an improvement. Now when I kill the
SY> external process I get:
SY> Invalid operation: SIGPIPE raised on process; closed it, "*GPG*"
SY> Which is what I'd expect to happen. OK, time for a big wild
SY> guess... It looks to me like the external process (in this case gpg)
SY> isn't getting any input, and XEmacs appears to hang because it's
SY> waiting for the external process to complete, but doesn't because the
SY> external process is waiting for input.
No, SIGPIPE means the external process has died, and XEmacs isn't
noticing in time. I think normally, it shouldn't ever get to this
piece of code.
SY> Let me know if I can do anything to help get to the bottom of this.
Set a break point on the invalid_operation call in unix_send_process
(around line 1569). Reproduce the error. Mail in the backtrace, if
possible both C and Lisp.
--
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla