Bug 2865 - time/tzfile.c doesn't set timezone correctly

Bug#:

2865 alias:

Hardware:

Reporter:

Martin Dittmar <mdittmar@linux-ag.de>

Host:

Target:

Build:

Product:

Add CC:

Component:

Version:

CC:

Remove selected CCs

Status:

RESOLVED

Priority:

Resolution:

WORKSFORME

Severity:

Assigned To:

Ulrich Drepper <drepper@redhat.com>

Target Milestone:

Flags:			Requestee:
	backport		()
	examined		()
	testsuite		()

Summary:

Keywords:

Attachment	Description	Type	Created	Actions
test.c	Short program to demonstrate the behaviour	text/x-csrc	2006-06-29 11:03	Edit None
tzfile.c-patch	Patch for 2.4 CVS version (29.6.2006)	patch	2006-06-29 11:05	Edit \| Diff
Create a New Attachment (proposed patch, testcase, etc.)			View All

Bug 2865 depends on:			Show dependency tree Show dependency graph
Bug 2865 blocks:			Show dependency tree Show dependency graph

Additional Comments:

Leave as RESOLVED WORKSFORME
Reopen bug
Mark bug as VERIFIED

View Bug Activity | Format For Printing

Description:

Last confirmed: 0000-00-00 00:00

Opened: 2006-06-29 11:00

method __tzfile_default in tzfile.c does not set "__use_tzfile = 0" at the end
of the method.

This leads to the problem, that the global variable "timezone" is not set
correctly if the env variable TZ is set e.g. to JKL3:10PNM4:40 (with the first
part being standard time and the second daylight saving time)
Then, timezone is set to a nonsense value of 18000 instead of the expected 11400

For a demonstration see the attached program.

Note: this bug blocks LSB conformance (LSB runtime tests T.ctime_X 1,
T.localtim_X 1, T.mktime_X 1)

Bug found in debian sarge system (libc 2.3.2) but is not yet fixed in CVS.

------- Additional Comment #1 From Martin Dittmar 2006-06-29 11:03 -------

Created an attachment (id=1126)
Short program to demonstrate the behaviour

Attached program to test tzset behaviour: The last printed timezone should be
11400, but is 18000.

------- Additional Comment #2 From Martin Dittmar 2006-06-29 11:05 -------

Created an attachment (id=1127)
Patch for 2.4 CVS version (29.6.2006)

------- Additional Comment #3 From Ulrich Drepper 2006-08-12 20:47 -------

The test program shows the expected result at least on recent systems.  And the
patch seems to be wrong in any case.  Unless you can provide a real explanation
or a test program I assume this is just a bug in debian's libc.