public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "egmont at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug locale/18927] New: Different strings should never collate as equal
Date: Sun, 06 Sep 2015 22:21:00 -0000 [thread overview]
Message-ID: <bug-18927-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=18927
Bug ID: 18927
Summary: Different strings should never collate as equal
Product: glibc
Version: 2.21
Status: NEW
Severity: normal
Priority: P2
Component: locale
Assignee: unassigned at sourceware dot org
Reporter: egmont at gmail dot com
Target Milestone: ---
Bug 13547 manually fixed a case where two distinct strings collated as equal.
Bug 16527 is another, currently unresolved case. Probably there are other, yet
undiscovered cases as well, and new ones might appear in the future.
This causes confusion with programs such as sort (the order is undefined, might
vary from run to run), or uniq (different lines being reported as equal).
I think there should be a safeguard code so that no locale definition can
result in this ever happening.
One possible approach I can imagine: Change the current strxfrm() magic to
produce an output that's restricted to bytes in the 2-255 range. Then append a
0x01 byte followed by the original string's literal copy.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2015-09-06 22:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-06 22:21 egmont at gmail dot com [this message]
2015-09-07 12:17 ` [Bug locale/18927] " fweimer at redhat dot com
2015-09-09 7:21 ` fweimer at redhat dot com
2015-09-09 8:13 ` egmont at gmail dot com
2015-09-09 8:15 ` egmont at gmail dot com
2015-09-09 8:37 ` egmont at gmail dot com
2015-09-09 10:21 ` joseph at codesourcery dot com
2015-09-09 11:10 ` egmont at gmail dot com
2015-09-09 11:41 ` fweimer at redhat dot com
2015-09-09 13:58 ` joseph at codesourcery dot com
2015-09-09 15:28 ` egmont at gmail dot com
2015-09-09 19:23 ` egmont at gmail dot com
2023-05-31 16:57 ` carenas at gmail dot com
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-18927-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).