| 1 |
#! /bin/sh |
| 2 |
# Test for a bug in glibc's regex code as of September 7, 2014. |
| 3 |
# |
| 4 |
# Copyright (C) 2014-2025 Free Software Foundation, Inc. |
| 5 |
# |
| 6 |
# Copying and distribution of this file, with or without modification, |
| 7 |
# are permitted in any medium without royalty provided the copyright |
| 8 |
# notice and this notice are preserved. |
| 9 |
|
| 10 |
# This tickles a bug in the regex code that can cause heap violations etc. |
| 11 |
# A fix would be welcome, though fixing is not trivial. See: |
| 12 |
# https://sourceware.org/bugzilla/show_bug.cgi?id=11053 |
| 13 |
|
| 14 |
. "${srcdir=.}/init.sh"; path_prepend_ ../src |
| 15 |
require_timeout_ |
| 16 |
|
| 17 |
echo a > in || framework_failure_ |
| 18 |
|
| 19 |
fail=0 |
| 20 |
|
| 21 |
# Clear this, so glibc doesn't bother to produce a core dump. |
| 22 |
MALLOC_CHECK_= |
| 23 |
|
| 24 |
warn_ "$ME_: expect malfunction on glibc systems due to" \ |
| 25 |
"https://sourceware.org/bugzilla/show_bug.cgi?id=11053" |
| 26 |
|
| 27 |
# While with glibc-2.35, it no longer aborts, the empty result is still wrong: |
| 28 |
timeout 10 grep -E '(.?)(.?)(.?)\3\2\1' in > out || fail=1 |
| 29 |
compare out in || fail=1 |
| 30 |
|
| 31 |
Exit $fail |