summaryrefslogtreecommitdiff
path: root/po
diff options
context:
space:
mode:
authorAssaf Gordon <assafgordon@gmail.com>2016-07-04 19:03:06 -0400
committerAssaf Gordon <assafgordon@gmail.com>2016-07-06 20:29:07 -0400
commit77a7c6a731acd4dea226b500c21dce17b2a94ece (patch)
tree4d4992fbf3624086b6a1daad6d9c594a621605be /po
parent0052daf1e5651c4772d75b595dfc714e0e20587e (diff)
downloadsed-77a7c6a731acd4dea226b500c21dce17b2a94ece.tar.gz
tests: skip tests upon buggy mbrtowc implementations
Sed tests purposefully use invalid non-utf8 multibyte sequences to test sed's handling of invalid input/program. Some implementations wrongly accept invalid sequences, causing false alarms. Add a test program to detect such buggy implementations and skip the tests if needed. See discussion in: http://lists.gnu.org/archive/html/sed-devel/2016-07/msg00005.html http://lists.gnu.org/archive/html/sed-devel/2016-07/msg00000.html http://lists.gnu.org/archive/html/sed-devel/2016-06/msg00031.html http://lists.gnu.org/archive/html/sed-devel/2016-06/msg00014.html * bootstrap.conf: Add gnulib's closeout module. * m4/.gitignore, lib/.gitignore, po/POTFILES.in: Adjust after adding closeout module. * testsuite/Makefile.am (check_PROGRAMS): Add new program. * testsuite/test-mbrtowc.c: New program. * testsuite/init.cfg (require_valid_ja_eucjp_locale_) (require_valid_ja_shiftjis_locale_): New functions. Call test-mbrtowc with known invalid multibyte sequences to ensure implementation is not buggy and rejects them; Skip test otherwise. * testsuite/invalid-mb-seq-UMR.sh: Use require_valid_ja_eucjp_locale_. * testsuite/mb-charclass-non-utf8.sh: Use require_valid_ja_shiftjis_locale_.
Diffstat (limited to 'po')
-rw-r--r--po/POTFILES.in1
1 files changed, 1 insertions, 0 deletions
diff --git a/po/POTFILES.in b/po/POTFILES.in
index 637bb7a..db55651 100644
--- a/po/POTFILES.in
+++ b/po/POTFILES.in
@@ -1,3 +1,4 @@
+lib/closeout.c
lib/copy-acl.c
lib/error.c
lib/getopt.c