public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sam at gentoo dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug stdio/30244] New: printf assertion fires in printf_fp when running coreutils' test suite (od crashes)
Date: Sat, 18 Mar 2023 23:45:57 +0000	[thread overview]
Message-ID: <bug-30244-131@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 30244
           Summary: printf assertion fires in printf_fp when running
                    coreutils' test suite (od crashes)
           Product: glibc
           Version: 2.37
            Status: NEW
          Severity: normal
          Priority: P2
         Component: stdio
          Assignee: unassigned at sourceware dot org
          Reporter: sam at gentoo dot org
  Target Milestone: ---
              Host: ia64-unknown-linux-gnu
            Target: ia64-unknown-linux-gnu
             Build: ia64-unknown-linux-gnu

Noticed when running the coreutils test suite on ia64. See
https://lists.gnu.org/archive/html/coreutils/2023-03/msg00063.html.

```
# seq 19 > in
# od -An -tfDz -tfLz in
  1.6292135911574872e-259  1.9544134620527668e-259  >1.2.3.4.5.6.7.8.<
Fatal glibc error: printf_fp.c:501 (__printf_fp_buffer_1): assertion failed: cy
== 1 || (p.frac[p.fracsize - 2] == 0 && p.frac[0] == 0)
Aborted
```

This is with sys-libs/glibc-2.37-r1 on Gentoo.

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

                 reply	other threads:[~2023-03-18 23:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-30244-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).