|
Home About Us A-Z Index Search * Contact Us Register Login Press ShopThe Open Brand -- Problem Reporting and Interpretations System |
Problem Report 0463 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 0463.
Report 0463 Actions
Problem Report Number 0463 Submitter's Classification Test Suite problem State Resolved Resolution Rejected (REJ) Problem Resolution ID REJ.X.0082 Raised 1994-06-14 08:00 Updated 2003-03-13 08:00 Published null Product Standard Internationalised System Calls and Libraries (XPG4) Certification Program The Open Brand certification program Test Suite VSX4 version 4.3.4 Test Identification XPG4.os/procenv/confstr 1 Problem Summary PG4R.083 According to the American National Standard for Information Systems - Programming Language C, Doc No. X3J11/90-013, 3.5.6 Type definitions, 'If an object that has automatic storage duration is not in... Problem Text
According to the American National Standard for Information Systems -
Programming Language C, Doc No. X3J11/90-013, 3.5.6 Type definitions,
'If an object that has automatic storage duration is not initialized
explicitly, its value is indeteminate.'
The variable buf[MAXVAL] is defined as a local variable. It should be
initialized in the test to zero. The suggested change is as follow:
/SCT/stds/xpg/vsx4/tset/XPG4.os/procenv/confstr/confstr.c
Line 278: add after DBUG_ENTER("test1");
for (i=0; i<MAXVAL;i++)
buf[i]=0;
Test Output
/tset/XPG4.os/procenv/confstr/T.confstr 1 Failed
Test Information:
confstr(_CS_PATH,buf,len) failed
when len < length of return value
expected 71 bytes written to buf[]
actually 73 bytes written to buf[]
confstr(_CS_PATH,buf,len) failed
when len = length of return value
expected 72 bytes written to buf[]
actually 73 bytes written to buf[]Review Information
Review Type TSMA Review Start Date null Completed null Status Complete Review Recommendation No Resolution Given Review Response
The description of confstr() in XSH4 states that:
"If the string to be returned is longer than len bytes, including the
terminating null, then confstr() truncates the string to len-1 bytes and
null-terminates the results."
It does not seem that the system under test is null-terminating the result
in this manner and is writing additional bytes bwyond those requested into
buf. It is not the responsibility of the application to fill the buffer
with null characters, but rather the responsibility of the implementation
to ensure that the string is null-terminated even if the string is longer
than the number of bytes specified in the call to confstr().
This does not seem to be a test suite deficiency and it is not recommended
that a waiver be granted.
Review Type SA Review Start Date null Completed null Status Complete Review Resolution Rejected (REJ) Review Conclusion
This request is refused.
Problem Reporting System Options:
- View Report 0463
- List All PRs
- Search Reports
- Email the System Administrator
- View the The Open Brand Interpretations Database User Manual
Contact the Certification Authority