public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "yann at droneaud dot fr" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug time/29461] New: strptime() failed to parse negative %s number of seconds since the Epoch, happily produced by strftime()
Date: Mon, 08 Aug 2022 19:29:40 +0000	[thread overview]
Message-ID: <bug-29461-131@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=29461

            Bug ID: 29461
           Summary: strptime() failed to parse negative %s number of
                    seconds since the Epoch, happily produced by
                    strftime()
           Product: glibc
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: time
          Assignee: unassigned at sourceware dot org
          Reporter: yann at droneaud dot fr
  Target Milestone: ---

Created attachment 14267
  --> https://sourceware.org/bugzilla/attachment.cgi?id=14267&action=edit
strftime(), strptime() %s format test with negative timestamp

strftime(,"%s",) can produce negative number of seconds since the Epoch for
date before the 1970-01-01, but strptime() refuses to parse negative numbers,
thus is unable to parse the string formatted by strftime().

For example, the attached test case reports the following:

    strftime() produced "-3600"
    strptime() failed to parse "-3600"

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2022-08-08 19:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-08 19:29 yann at droneaud dot fr [this message]
2022-08-08 19:58 ` [Bug time/29461] " sam at gentoo dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-29461-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).