|
Home About Us A-Z Index Search * Contact Us Register Login Press ShopThe Open Brand -- Problem Reporting and Interpretations System |
Problem Report 2562 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 2562.
Report 2562 Actions
Problem Report Number 2562 Submitter's Classification Test Suite problem State Resolved Resolution Permanent Interpretation (PIN) Problem Resolution ID PIN.X.0285 Raised 2011-03-10 11:44 Updated 2011-03-30 07:27 Published 2011-03-30 07:27 Product Standard Internationalised System Calls and Libraries Extended V3 (UNIX 03) Certification Program The Open Brand certification program Test Suite VSRT version 5.4.3 Test Identification POSIX_rte.os/procprim/posix_spawn/T.posix_spawn.55 Specification Base Definitions Issue 6 Location in Spec Line 46880 [XSH posix_spawn_file_actions_add_close] Linked Problem Reports 2616 Problem Summary POSIX_rte.os/procprim/posix_spawn/T.posix_spawn test 55 fails due to not
reporting EBADF when closing an already closed fdProblem Text The current test does not reflect the change documented in Austin Group
Defect 370:
0000370: addclose should not cause posix_spawn to fail if closing an
already closed fd
which clarifies that closing an already closed fd should not result in
EBADF. While that change is implemented in Issue 7, it would appear
clear that reporting EBADF due to closing an already closed fd was not
the intent and is not the desired action going forward.Test Output **************************************************************************************
/tset/POSIX_rte.os/procprim/posix_spawn/T.posix_spawn 55
Failed
Test Description:
If the symbol {_POSIX_SPAWN} is defined or the imple-
mentation supports the posix_spawn(pid, path,
file_actions, attrp, argv[], envp[]) function:
When file_actions contains an close action and
fildes is not a valid file descriptor, then
posix_spawn(pid, path, file_actions, attrp, argv[],
envp[]) returns EBADF or posix_spawn(pid, path,
file_actions, attrp, argv[], envp[]) returns zero
and the child process exits with an exit status of
127.
Test Strategy:
Error: requested file not found in archive
/export/test/TET3.6/vsx/MAN/tset/POSIX_rte.os/procprim/posix_spawn/L.posix_spawn_s
Test Information:
posix_spawn returned 0 err 9 EBADF and child return 0
**************************************************************************************Review Information
Review Type TSMA Review Start Date 2011-03-10 03:44 Last Updated 2011-03-10 11:18 Completed 2011-03-10 11:18 Status Complete Review Recommendation Rejected (REJ) Review Response Austin Group Defect 370 is currently just a proposed change to be made
in the next revision of the standard. In this form, it will not have
any effect on the requirements of the standard until that revision
(Issue 8) is approved.
If implementors wish to be able to make this change to their systems
before Issue 8 is approved, they should ask the Austin Group to reopen
defect 370 and process it as an interpretation with a response
containing the key phrase "concerns have been raised about this which
are being referred to the sponsor".
Review Type SA Review Start Date 2011-03-10 19:18 Last Updated 2011-03-10 11:21 Completed 2011-03-10 11:21 Status Complete Review Resolution Rejected (REJ) Review Conclusion Austin Group Defect 370 is currently just a proposed change to be made
in the next revision of the standard. In this form, it will not have
any effect on the requirements of the standard until that revision
(Issue 8) is approved.
If implementors wish to be able to make this change to their systems
before Issue 8 is approved, they should ask the Austin Group to reopen
defect 370 and process it as an interpretation with a response
containing the key phrase "concerns have been raised about this which
are being referred to the sponsor".
Problem Reporting System Options:
- View Report 2562
- List All PRs
- Search Reports
- Email the System Administrator
- View the The Open Brand Interpretations Database User Manual
Contact the Certification Authority