glibc/posix/tst-fnmatch7.c
Andreas Schwab 8442f0d966 Fix handling of unterminated bracket expressions in fnmatch (bug 28792)
When fnmatch processes a bracket expression, and eventually finds it to be
unterminated, it should rescan it, treating the starting bracket as a
normal character.  That didn't happen when a matching character was found
while scanning the bracket expression.
2022-01-24 17:13:33 +01:00

38 lines
1.4 KiB
C

/* Test for fnmatch handling of unterminated bracket expression (bug 28792)
Copyright (C) 2022 Free Software Foundation, Inc.
This file is part of the GNU C Library.
The GNU C Library is free software; you can redistribute it and/or
modify it under the terms of the GNU Lesser General Public
License as published by the Free Software Foundation; either
version 2.1 of the License, or (at your option) any later version.
The GNU C Library is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
Lesser General Public License for more details.
You should have received a copy of the GNU Lesser General Public
License along with the GNU C Library; if not, see
<https://www.gnu.org/licenses/>. */
#include <fnmatch.h>
#include <support/check.h>
static int
do_test (void)
{
/* An unterminated bracket expression should be rescanned, treating the
open bracket as a normal character. The backslash causes the close
bracket to be treated as a normal character, not ending the bracket
expression. */
TEST_VERIFY (fnmatch ("[", "[", 0) == 0);
TEST_VERIFY (fnmatch ("[[", "[[", 0) == 0);
TEST_VERIFY (fnmatch ("[\\]", "[]", 0) == 0);
TEST_VERIFY (fnmatch ("[[\\]", "[[]", 0) == 0);
return 0;
}
#include <support/test-driver.c>