Interpretations

Answering questions that may arise related to the meaning of portions of an IEEE standard concerning specific applications.

IEEE Standards Interpretations for IEEE Std 1003.1™-2001 IEEE Standard for Information Technology - Portable Operating System Interface (POSIX®)

Copyright © 2006 by the Institute of Electrical and Electronics Engineers, Inc. 3 Park Avenue New York, New York 10016-5997 USA All Rights Reserved.

Interpretations are issued to explain and clarify the intent of a standard and do not constitute an alteration to the original standard. In addition, interpretations are not intended to supply consulting information. Permission is hereby granted to download and print one copy of this document. Individuals seeking permission to reproduce and/or distribute this document in its entirety or portions of this document must contact the IEEE Standards Department for the appropriate license. Use of the information contained in this document is at your own risk.

IEEE Standards Department Copyrights and Permissions 445 Hoes Lane, Piscataway, New Jersey 08855-1331, USA

Interpretation Request #31
Topic:exit should not invoke cancellation cleanup handlers or per-thread data destructors Relevant Sections: XSH exit

"exit()" should behave the same as _exit() or _Exit() with respect to cancellation cleanup handlers and per-thread data destructors. Replace Threads terminated by a call to _Exit() or _exit() shall not invoke their cancellation cleanup handlers or per-thread data destructors. with Termination of a process shall not invoke any thread cancellation cleanup handlers or per-thread data destructors.

Interpretation Response
The standards states the requirements for exit(), and conforming implementations must conform to this. However, concerns have been raised about this which are being referred to the sponsor.

Rationale for Interpretation
None.

Notes to the Editor (not part of this interpretation)
exit() should be described on a separate page that explains at the end that exit() inherits the behavior described separately for _exit()