public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "luigighiron at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug string/28898] mbrtoc16 segfaults when counting wide characters
Date: Sat, 04 May 2024 04:28:14 +0000	[thread overview]
Message-ID: <bug-28898-131-UkMb57Ltay@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28898-131@http.sourceware.org/bugzilla/>

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

Halalaluyafail3 <luigighiron at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |luigighiron at gmail dot com

--- Comment #3 from Halalaluyafail3 <luigighiron at gmail dot com> ---
This still seems to happen, also I think it is worth mentioning that the
current text of the standard does say "Subsequent calls will store successive
wide characters without consuming any additional input until all the characters
have been stored." so this could be interpreted as allowing for this crash to
happen since no mention of null here is made (though I do not think that this
was intended).

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

      parent reply	other threads:[~2024-05-04  4:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-16  6:41 [Bug string/28898] New: " mbuilov at gmail dot com
2023-06-26 13:23 ` [Bug string/28898] " bruno at clisp dot org
2023-06-26 13:27 ` bruno at clisp dot org
2024-05-04  4:28 ` luigighiron at gmail dot com [this message]

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-28898-131-UkMb57Ltay@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).