From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.bugs Subject: Re: Emacs current-time-string core dump on 64-bit hosts Date: Sat, 25 Mar 2006 10:26:23 -0500 Message-ID: References: <87k6arnqsx.fsf@penguin.cs.ucla.edu> <87fyle6luu.fsf@penguin.cs.ucla.edu> <877j6j1re8.fsf@penguin.cs.ucla.edu> Reply-To: rms@gnu.org NNTP-Posting-Host: main.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: sea.gmane.org 1143497986 27619 80.91.229.2 (27 Mar 2006 22:19:46 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 27 Mar 2006 22:19:46 +0000 (UTC) Cc: bug-gnu-emacs@gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Mar 28 00:19:41 2006 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1FO03V-0004aK-NS for geb-bug-gnu-emacs@m.gmane.org; Tue, 28 Mar 2006 00:19:22 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FO03U-0004vx-Ni for geb-bug-gnu-emacs@m.gmane.org; Mon, 27 Mar 2006 17:19:20 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FNAen-00077X-RW for bug-gnu-emacs@gnu.org; Sat, 25 Mar 2006 10:26:25 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FNAen-00077L-0E for bug-gnu-emacs@gnu.org; Sat, 25 Mar 2006 10:26:25 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FNAem-00077I-N5 for bug-gnu-emacs@gnu.org; Sat, 25 Mar 2006 10:26:24 -0500 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.52) id 1FNAfq-0002mE-I2 for bug-gnu-emacs@gnu.org; Sat, 25 Mar 2006 10:27:30 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1FNAel-000088-VG; Sat, 25 Mar 2006 10:26:24 -0500 Original-To: Paul Eggert In-reply-to: <877j6j1re8.fsf@penguin.cs.ucla.edu> (message from Paul Eggert on Fri, 24 Mar 2006 13:09:35 -0800) X-BeenThere: bug-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:14998 Archived-At: But the current time might be out of ctime's range for many reasons: * a hardware problem (the hardware clock jumped far in the future or past) * a software problem (a bug in the 'date' program's date parser, say) * a human error (someone set the date incorrectly). It seems unlikely to me that these things will be able to set the system's time to a value the system can't handle. More likely the time will get truncated into the range the system can handle. For instance, if someone specifies an out-of-range date, it will probably be truncated into a reasonable date. It will just be incorrect. Meanwhile, the system will probably crash due to demons that use ctime.