This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug time/24630] mktime fails with certain timezones since glibc 2.28: "Value too large for defined data type"
- From: "winter-gcc at bfw-online dot de" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Thu, 26 Sep 2019 12:31:59 +0000
- Subject: [Bug time/24630] mktime fails with certain timezones since glibc 2.28: "Value too large for defined data type"
- Auto-submitted: auto-generated
- References: <bug-24630-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24630
--- Comment #10 from winter-gcc@bfw-online.de ---
(In reply to Florian Weimer from comment #7)
> (In reply to Oliver Smith from comment #6)
> > I could not find a source that says using mktime with UTC is not allowed.
> > Would you mind explaining why that is the case?
>
> tm_isdst == 1 for UTC is invalid input for mktime. It is unclear what you
> are trying to accomplish.
The previous behavior of TZ=UTC mktime was like timegm. It is still is, except
when tm_isdst = 1.
The man page does not reflect this fact strongly. Also EOVERFLOW is quite
missleading, maybe EINVAL would be better?
--
You are receiving this mail because:
You are on the CC list for the bug.