🚀 go-pugleaf

mush has recently started aborting (at startup) with a segmentation
violation error.  I have been unable to find any reason why.  It has
worked for several months without a problem.  If I invoke it with
debugging on (-d option), it will source the systemwide mushrc, and then
my personal mushrc, then abort with the error.  I haven't made any
changes recently to the system (that I know of anyway) which would cause
this.

I've tried removing both the systemwide mushrc and my personal mushrc
with no change in behavior.  I was also 3 or 4 patches behind, so I
rebuilt with all current patches applied with no change.  I've tried
building it with INTERNAL_MALLOC defined and undefined with no change.
The problem occurs regardless of the user-id that invoked mush.
I've also tried fsck'ing with no abnormal results, and the system
passes the Power On Self Test OK.  This is a Sperry IT (286) system
running SCO xenix 2.2.3.

I did notice something peculiar a couple of days before this started.
A couple of messages were displayed with a "_" in the place where the
day of the week should have been, even though looking at my mail file
showed everything to be normal.  The following is the hdr_format
command in my .mushrc.
    set hdr_format='%14a %D %M %-2N %5T  %-3l/%5c "%.24s"'

I'm at a loss as to what I should look at next.  Anyone have any
suggestions?

Thanks, Roger
--
Roger A. Cornelius           rac@sherpa            uunet!sherpa!rac