From: Richard Stallman <rms@gnu.org>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: Emacs current-time-string core dump on 64-bit hosts
Date: Sat, 25 Mar 2006 10:26:23 -0500 [thread overview]
Message-ID: <E1FNAel-000088-VG@fencepost.gnu.org> (raw)
In-Reply-To: <877j6j1re8.fsf@penguin.cs.ucla.edu> (message from Paul Eggert on Fri, 24 Mar 2006 13:09:35 -0800)
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.
next prev parent reply other threads:[~2006-03-25 15:26 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-17 5:58 Emacs current-time-string core dump on 64-bit hosts Paul Eggert
2006-03-17 12:16 ` Eli Zaretskii
2006-03-17 12:46 ` Andreas Schwab
2006-03-17 16:04 ` Kevin Rodgers
2006-03-18 0:44 ` Paul Eggert
2006-03-18 11:50 ` Eli Zaretskii
2006-03-19 2:30 ` Paul Eggert
2006-03-21 19:25 ` Richard Stallman
2006-03-18 8:43 ` Richard Stallman
2006-03-19 1:53 ` Paul Eggert
2006-03-19 21:50 ` Richard Stallman
2006-03-19 23:44 ` Paul Eggert
2006-03-20 19:59 ` Eli Zaretskii
2006-03-27 22:00 ` Paul Eggert
2006-03-28 10:16 ` Eli Zaretskii
2006-03-30 7:52 ` Paul Eggert
2006-03-30 20:36 ` Eli Zaretskii
2006-04-04 4:57 ` Paul Eggert
2006-04-04 18:20 ` Eli Zaretskii
2006-03-21 1:00 ` Richard Stallman
2006-03-24 20:45 ` Paul Eggert
2006-03-25 9:10 ` Eli Zaretskii
2006-03-26 5:25 ` Paul Eggert
2006-03-26 20:06 ` Eli Zaretskii
2006-03-27 22:29 ` Richard Stallman
2006-03-28 10:20 ` Eli Zaretskii
2006-03-29 8:14 ` Richard Stallman
2006-03-25 15:26 ` Richard Stallman
2006-03-24 21:00 ` Paul Eggert
2006-03-24 21:09 ` Paul Eggert
2006-03-25 15:26 ` Richard Stallman [this message]
2006-03-26 7:31 ` Paul Eggert
[not found] ` <E1FNnCd-0000pN-J4@fencepost.gnu.org>
2006-03-27 20:49 ` Paul Eggert
2006-03-28 19:33 ` Richard Stallman
2006-03-30 7:57 ` Paul Eggert
2006-03-31 17:28 ` Richard Stallman
2006-03-31 20:51 ` Paul Eggert
2006-04-01 20:28 ` Richard Stallman
2006-04-03 4:44 ` Paul Eggert
2006-03-17 16:25 ` Andreas Schwab
-- strict thread matches above, loose matches on Subject: below --
2006-03-17 8:02 Paul Eggert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1FNAel-000088-VG@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=bug-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).