public inbox for bzip2-devel@sourceware.org
 help / color / mirror / Atom feed
From: "pmqs at outlook dot com" <sourceware-bugzilla@sourceware.org>
To: bzip2-devel@sourceware.org
Subject: [Bug bzip2/28283] undefined behavior for isdigit and isspace
Date: Tue, 27 Dec 2022 12:34:16 +0000	[thread overview]
Message-ID: <bug-28283-11876-0Vz8g9fSVS@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28283-11876@http.sourceware.org/bugzilla/>

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

Paul Marquess <pmqs at outlook dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pmqs at outlook dot com

--- Comment #1 from Paul Marquess <pmqs at outlook dot com> ---
This issue has been reported downstream in the Perl sources, which include a
sub-set of the bzip2 source. Believe that OpenBSD is a candidate for this issue
causing a problem.

Also, see
https://wiki.sei.cmu.edu/confluence/display/c/STR37-C.+Arguments+to+character-handling+functions+must+be+representable+as+an+unsigned+char
for details on a coding standard that mentions the isdigit issue.

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

  reply	other threads:[~2022-12-27 12:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-27 17:31 [Bug bzip2/28283] New: " roland.illig at gmx dot de
2022-12-27 12:34 ` pmqs at outlook dot com [this message]
2022-12-27 17:24 ` [Bug bzip2/28283] " mark at klomp dot org
2024-04-09 13:31 ` email at arsoftware dot net.br
2024-04-09 19:19 ` mark at klomp 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-28283-11876-0Vz8g9fSVS@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=bzip2-devel@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).