[5331] in SIPB bug reports
Re: dclock
daemon@ATHENA.MIT.EDU (rain)
Tue Apr 25 00:17:39 1995
To: Kimathi Hardy <ktc@MIT.EDU>
Cc: bug-sipb@MIT.EDU
In-Reply-To: Your message of "Mon, 24 Apr 1995 23:47:56 EDT."
<9504250347.AA00724@w20-575-125.MIT.EDU>
Date: Tue, 25 Apr 1995 00:17:06 EDT
From: rain <yandros@MIT.EDU>
Recently, a friend and fellow sipb-locker-maintainer noticed that
running dclock on a sparc classic caused it to immeditately exit and
dump core (you wouldn't have seen the message about this; the `>&
/dev/null' part explictly throws these error messages away). I was at
a loss to explain why the program would suddenly die like this, since
it hadn't been changed in LONG time (more than a year? I forget). He
recompiled the program to see if he could debug the problem, and it
mysteriously went away.
A couple days later, he told me that the problem was back. Then it
went away again.
So, if this happens to you again, could you please:
o run it from an xterm (just `athena% dclock') and see what it says.
o if it says something like `segmentation fault (core dumped)', try
it on a different machine, if you can.
o in any case, let me know what happened.
thanks,
chad
