|
Home About Us A-Z Index Search * Contact Us Register Login Press ShopThe Open Brand -- Problem Reporting and Interpretations System |
Problem Report 2291 Details
Show help | Quick Search | Submit a Test Suite Support Request | Click here to view your privileges
This page provides all information on Problem Report 2291.
Report 2291 Actions
Problem Report Number 2291 Submitter's Classification Specification problem State Resolved Resolution Test Suite Deficiency (TSD) Problem Resolution ID TSD.X.1174 Raised 2003-12-04 03:20 Updated 2003-12-10 14:12 Published 2003-12-10 14:12 Product Standard Internationalised System Calls and Libraries Extended V3 (UNIX 03) Certification Program The Open Brand certification program Test Suite VSX4 version 4.5.4 Test Identification XPG4.os/genuts/regcomp assertions: 30, 32, 34, 36, 38 Specification Base Definitions Issue 6 Location in Spec 37570 in the XSH PDF document Problem Summary PIN requested for legacy grey area in UNIX03 spec Problem Text For UNIX98, TIN.X.0086 and TIN.X.0087 were issued to track this grey
area in the SUSv2 spec. The wording was carried into the SUSv3 spec
without change. A single PIN is requested to waive these failures for
UNIX03 certifications.Test Output
************************************************************************
/tset/XPG4.os/genuts/regcomp/T.regcomp 30 Failed
Test Description:
If regcomp() is supported:
When the REG_EXTENDED flag is set in cflags, and pattern
contains
a {} imbalance, then a call to regcomp(preg, pattern, cflags)
returns either REG_EBRACE or REG_BADPAT.
Otherwise:
A call to regcomp() returns REG_ENOSYS and sets errno to ENOSYS.
Test Strategy:
CREATE pattern with xyab{3,}jkl{
CALL regcomp() with pattern and cflags set to REG_EXTENDED
VERIFY that regcomp() returned either REG_EBRACE or REG_BADPAT
Test Information:
regcomp(preg, "xyab{3,}jk{", REG_EXTENDED) returned 0 (No Error)
expected 9 (REG_EBRACE) or 2 (REG_BADPAT)
************************************************************************
************************************************************************
/tset/XPG4.os/genuts/regcomp/T.regcomp 32 Failed
Test Description:
If regcomp() is supported:
When the REG_EXTENDED flag is set in cflags, and pattern
contains
an expression of the form "{m,n}", "{m,}" or "{m}", in which
either m or n is not a number, then a call to regcomp(preg,
pattern, cflags) returns either REG_BADBR or REG_BADPAT.
Otherwise:
A call to regcomp() returns REG_ENOSYS and sets errno to ENOSYS.
Test Strategy:
CREATE pattern with 890magIFd{0,j} , 890magIFD{k,3} ,
890magIFD{k,} ,
890magIFD{k}
CALL regcomp() with pattern and cflags set to REG_EXTENDED
VERIFY that regcomp() returned either REG_BADBR or REG_BADPAT
Test Information:
regcomp(preg, "890magIFd{0,%}", REG_EXTENDED) returned 0 (No Error)
expected 10 (REG_BADBR) or 2 (REG_BADPAT)
regcomp(preg, "890magIFd{%,3}", REG_EXTENDED) returned 0 (No Error)
expected 10 (REG_BADBR) or 2 (REG_BADPAT)
regcomp(preg, "890magIFd{%,}", REG_EXTENDED) returned 0 (No Error)
expected 10 (REG_BADBR) or 2 (REG_BADPAT)
regcomp(preg, "890magIFd{!}", REG_EXTENDED) returned 0 (No Error)
expected 10 (REG_BADBR) or 2 (REG_BADPAT)
************************************************************************
************************************************************************
/tset/XPG4.os/genuts/regcomp/T.regcomp 34 Failed
Test Description:
If regcomp() is supported:
When the REG_EXTENDED flag is set in cflags, and pattern
contains
an expression of the form "{m,n}", "{m,}" or "{m}", in which
either m or n is greater than {RE_DUP_MAX}, then a call to
regcomp(preg, pattern, cflags) returns either REG_BADBR or
REG_BADPAT.
Otherwise:
A call to regcomp() returns REG_ENOSYS and sets errno to ENOSYS.
Test Strategy:
CREATE pattern with {0,RE_DUP_MAX+1}, {RE_DUP_MAX+1,n},
{RE_DUP_MAX+1,}, {RE_DUP_MAX+1}
CALL regcomp() with pattern and cflags set to REG_EXTENDED
VERIFY that regcomp() returned either REG_BADBR or REG_BADPAT
Test Information:
regcomp(preg, "890magIFd{0,256}", REG_EXTENDED) returned 0 (No
Error)
expected 10 (REG_BADBR) or 2 (REG_BADPAT)
regcomp(preg, "890magIFd{256,3}", REG_EXTENDED) returned 0 (No
Error)
expected 10 (REG_BADBR) or 2 (REG_BADPAT)
regcomp(preg, "890magIFd{256,}", REG_EXTENDED) returned 0 (No Error)
expected 10 (REG_BADBR) or 2 (REG_BADPAT)
regcomp(preg, "890magIFd{256}", REG_EXTENDED) returned 0 (No Error)
expected 10 (REG_BADBR) or 2 (REG_BADPAT)
************************************************************************
************************************************************************
/tset/XPG4.os/genuts/regcomp/T.regcomp 36 Failed
Test Description:
If regcomp() is supported:
When the REG_EXTENDED flag is set in cflags, and pattern
contains
a {} expression with more than two numbers, then a call to
regcomp(preg, pattern, cflags) returns either REG_BADBR or
REG_BADPAT.
Otherwise:
A call to regcomp() returns REG_ENOSYS and sets errno to ENOSYS.
Test Strategy:
CREATE pattern with {4,5,7}
CALL regcomp() with pattern and cflags set to REG_EXTENDED
VERIFY that regcomp() returned either REG_BADBR or REG_BADPAT
Test Information:
regcomp(preg, "xy{4,5,7}zabc", REG_EXTENDED) returned 0 (No Error)
expected 10 (REG_BADBR) or 2 (REG_BADPAT)
************************************************************************
************************************************************************
/tset/XPG4.os/genuts/regcomp/T.regcomp 38 Failed
Test Description:
If regcomp() is supported:
When the REG_EXTENDED flag is set in cflags, and pattern
contains
an expression of the form "{m,n}", in which m is greater than n,
then a call to regcomp(preg, pattern, cflags) returns either
REG_BADBR or REG_BADPAT.
Otherwise:
A call to regcomp() returns REG_ENOSYS and sets errno to ENOSYS.
Test Strategy:
CREATE pattern with {3,1}
CALL regcomp() with pattern and cflags set to REG_EXTENDED
VERIFY that regcomp() returned either REG_BADBR or REG_BADPAT
Test Information:
regcomp(preg, "def{3,1}cba", REG_EXTENDED) returned 0 (No Error)
expected 10 (REG_BADBR) or 2 (REG_BADPAT)
************************************************************************Review Information
Review Type SA Review Start Date 2003-12-04 03:20 Last Updated 2003-12-10 05:20 Completed 2003-12-10 05:20 Status Complete Review Resolution Test Suite Deficiency (TSD) Review Conclusion A TSD is granted for this PR
Problem Reporting System Options:
- View Report 2291
- List All PRs
- Search Reports
- Email the System Administrator
- View the The Open Brand Interpretations Database User Manual
Contact the Certification Authority