From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15347 invoked by alias); 6 Dec 2004 22:41:19 -0000 Mailing-List: contact glibc-bugs-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sources.redhat.com Received: (qmail 15222 invoked by uid 48); 6 Dec 2004 22:41:15 -0000 Date: Mon, 06 Dec 2004 22:41:00 -0000 Message-ID: <20041206224115.15221.qmail@sourceware.org> From: "jakub at redhat dot com" To: glibc-bugs@sources.redhat.com In-Reply-To: <20041206211946.601.kreckel@ginac.de> References: <20041206211946.601.kreckel@ginac.de> Reply-To: sourceware-bugzilla@sources.redhat.com Subject: [Bug libc/601] mktime(3) unreliable after calling tzset(3) when TZ is NULL or bogus X-Bugzilla-Reason: CC X-SW-Source: 2004-12/txt/msg00020.txt.bz2 List-Id: ------- 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.