From xemacs-m  Wed Feb 26 10:10:24 1997
Received: from neal.ctd.comsat.com (exim@neal.ctd.comsat.com [134.133.40.21])
	by xemacs.org (8.8.5/8.8.5) with SMTP id KAA16423
	for <xemacs-beta@xemacs.org>; Wed, 26 Feb 1997 10:10:24 -0600 (CST)
Received: from neal by neal.ctd.comsat.com with local (Exim 1.58 #2)
	id 0vzlun-0000yf-00; Wed, 26 Feb 1997 11:09:09 -0500
To: Simon Marshall <Simon.Marshall@esrin.esa.it>
Cc: XEmacs Beta <xemacs-beta@xemacs.org>
Subject: Re: Warning weird problem alert
References: <9702261547.AA28522@mail.esrin.esa.it>
Mime-Version: 1.0 (generated by tm-edit 7.105)
Content-Type: text/plain; charset=US-ASCII
From: Neal Becker <neal@ctd.comsat.com>
Date: 26 Feb 1997 11:09:09 -0500
In-Reply-To: Simon Marshall's message of Wed, 26 Feb 97 15:47:35 GMT
Message-ID: <u9ohd7v9ay.fsf@neal.ctd.comsat.com>
Lines: 16
X-Mailer: Gnus v5.4.15/XEmacs 20.1

>>>>> "Simon" == Simon Marshall <Simon.Marshall@esrin.esa.it> writes:

    >>> Now get this.  On two different xemacs on two different machines I have
    >>> the time frozen at 4:18am.  What's that all about?

    Tomasz> Exactly the same thing happened to me.

    Simon> I'll put a curse on anyone who says it happens when they load lazy-lock.el.


No, lazy lock is already backed down to previous version.

I'm guessing it may be related to itimer.  I redumped another xemacs
with itimer-1.02.  I haven't seen this happen to the new version, but
I never found a reliable way to reproduce it either.  OTOH, two
old xemacs's stopped at 4:18 am, the new one is still ticking.

