From: Eli Zaretskii <eliz@gnu.org>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: Emacs current-time-string core dump on 64-bit hosts
Date: Thu, 30 Mar 2006 22:36:31 +0200 [thread overview]
Message-ID: <uacb7brg0.fsf@gnu.org> (raw)
In-Reply-To: <877j6c74jk.fsf@penguin.cs.ucla.edu> (message from Paul Eggert on Wed, 29 Mar 2006 23:52:31 -0800)
> Cc: bug-gnu-emacs@gnu.org
> From: Paul Eggert <eggert@CS.UCLA.EDU>
> Date: Wed, 29 Mar 2006 23:52:31 -0800
>
> from what you write, the comment actually means that, given code
> like this:
>
> t = time (NULL);
> p = ctime (&t);
>
> then p is NULL when "." is a networked directory. Am I understanding
> you correctly now?
Yes, that's what I meant. But I cannot prove that my understanding is
correct, since all I have is the comment text, and not further
evidence.
> Hmm, but if that's the case, why can't w32.c and ntlib.c use this
> wrapper instead?
>
> char *
> sys_ctime (const time_t *t)
> {
> return asctime (localtime (t));
> }
>
> Is it possible that the actual bug with networked drives is in
> localtime, not in ctime? If so, shouldn't localtime be wrapped?
>
> But localtime is used in a bunch of places, so I'd be a bit surprised
> if it needed to be wrapped.
>
> Or perhaps asctime needs to be wrapped? That would be really strange;
> I can't imagine why that would be.
>
> (Can you tell that I'm somewhat at sea when reasoning about the
> behavior of Microsoft Windows? :-)
We all are at sea there.
Is there some Windows guru here who could resolve the issue?
> Anyway, I think your last draft comment sounds reasonable, though I'd
> like to understand the bug better before worrying about the details
> there.
Yep, me too. But if no one responds, I think we should do as best as
we understand it now.
next prev parent reply other threads:[~2006-03-30 20:36 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 [this message]
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
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=uacb7brg0.fsf@gnu.org \
--to=eliz@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).