Thank you for your answer, I appreciate it.
I've read the standard and it is clear to me I need to review my code. You
were right.
Comments in the bug report misleaded me. Somebody should add
a note about this standard and point out this could be a programming
error and not a glibc bug.
Thank you very much for you help again!
Best regards, Zoltan
On Tue, 13 Jun 2006, Gabor Gombas wrote:
On Tue, Jun 13, 2006 at 10:48:05AM +0200, Kecskemethy Zoltan wrote:
Recently I upgraded my woody webserver to sarge. Now I have
2.3.2.ds1-22sarge3 version of libc6 package installed on my system.
Our websites uses mktime php funciton and it seems it gives us back wrong
data because of a glibc bug.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=196177
When we use date before year 1970. It seems
to me our stable package still has this bug in it. :(
To me it seems the bug is in the application, not in glibc. time_t is
defined as "seconds elapsed since 00:00:00 on January 1, 1970,
Coordinated Universal Time (UTC)", so it by definition can not represent
date values before 1970. SUSv3 says about mktime: "If the time since the
Epoch cannot be represented, the function shall return the value
(time_t)-1."
Gabor
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
