This is the mail archive of the glibc-bugs@sources.redhat.com mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libc/601] mktime(3) unreliable after calling tzset(3) when TZ is NULL or bogus


------- Additional Comments From jakub at redhat dot com  2004-12-06 22:41 -------
Calling setenv with second argument NULL is a bug, just don't do that.
The man page you are citing is badly worded and inaccurate, e.g. it is not
possible to have a variable set in the environment, but its value NULL,
probably it means its value being an empty string.
For the "#!@+*%&" value you shouldn't rely on anything, certainly no standard
requires any specific behaviour and the man page is not what determines glibc
behaviour.
But I'll post a patch that will in that case make the offset 0 rather than -1L.

-- 


http://sources.redhat.com/bugzilla/show_bug.cgi?id=601

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]