bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Emacs current-time-string core dump on 64-bit hosts


From: Eli Zaretskii
Subject: Re: Emacs current-time-string core dump on 64-bit hosts
Date: Thu, 30 Mar 2006 22:36:31 +0200

> Cc: address@hidden
> From: Paul Eggert <address@hidden>
> 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.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]