Andrew Hobson <ahobson(a)eng.mindspring.net> writes in xemacs-beta(a)xemacs.org:
 On 12 Oct 1998 15:03:54 -0700, SL Baur <steve(a)xemacs.org>
said:
> These are the identical symptoms to the bug I might have isolated a
> test case for and posted about last week.  Does uudecdoing the XEmacs
> killer jpeg crash XEmacs for you? 
 No.  I tried it with both FreeBSD's uudecode and GNU's
uudecode from
 sharutils-4.2.  The killer jpeg causes uudecode to exit immediately with
 an error.  My FreeBSD uudecode reports: 
 uudecode: stdin: illegal ~user 
 So on a hunch, I replaced my uudecode with: 
 #!/bin/sh
 exit 0 
 I immediately got a crash. 
That would be positive ...
 But I just tried it three more times and I didn't. 
... but that isn't.
 I know I'm stating the obvious, but I guess it's a race
condition. 
Yes, that is likely.  The code says there's a SIGPIPE handler
installed, but somehow it sometimes isn't.  In my case, the killer
jpeg is a sure kill.
This bug isn't new.  It's been around for a long time -- at least back 
to 20.3, I think.
 Come to think of it, after my initial crash, I did a netstat -t and
I
 noticed that I didn't have a connection to the news server.  I didn't
 think much about it at the time.