public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "harald at gigawatt dot nl" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug glob/26620] New: fnmatch with collating symbols results in segmentation fault
Date: Tue, 15 Sep 2020 21:23:45 +0000	[thread overview]
Message-ID: <bug-26620-131@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 26620
           Summary: fnmatch with collating symbols results in segmentation
                    fault
           Product: glibc
           Version: 2.32
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: glob
          Assignee: unassigned at sourceware dot org
          Reporter: harald at gigawatt dot nl
  Target Milestone: ---

Consider this test program:

  #include <stdio.h>
  #include <locale.h>
  #include <fnmatch.h>
  int main(int argc, char *argv[]) {
    setlocale(LC_ALL, "");
    if (argc != 3) {
      fprintf(stderr, "usage: fnmatch <pattern> <string>\n");
      return 2;
    }
    return !!fnmatch(argv[1], argv[2], 0);
  }

When called as

  export LC_ALL=en_US.UTF-8
  ./fnmatch $'[[.L\u00B7.]]' . # [[.L·.]]

This results in a segmentation fault in internal_fnwmatch.

Seen on glibc 2.32 built with GCC 10.2.0, also reproducible with the
libc6-2.31-0ubuntu9 provided by Ubuntu 20.04 for amd64.

(I think there are a few more bugs in there that do not result in a crash, but
do result in a wrong return value. Should I include the details in here or
report that separately?)

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

             reply	other threads:[~2020-09-15 21:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-15 21:23 harald at gigawatt dot nl [this message]
2020-09-16 13:12 ` [Bug glob/26620] " schwab@linux-m68k.org
2020-11-11 12:38 ` fweimer at redhat 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-26620-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).