|
Viewing Issue Simple Details
[ Jump to Notes ]
|
[ Issue History ]
[ Print ]
|
|
ID |
Category |
Severity |
Type |
Date Submitted |
Last Update |
|
0001363 |
[Issue 8 drafts] System Interfaces |
Comment |
Enhancement Request |
2020-07-03 13:44 |
2024-06-11 09:12 |
|
|
Reporter |
geoffclare |
View Status |
public |
|
|
Assigned To |
|
|
Priority |
normal |
Resolution |
Accepted |
|
|
Status |
Closed |
|
Product Version |
Draft 1 |
|
|
Name |
Geoff Clare |
|
Organization |
The Open Group |
|
User Reference |
|
|
Section |
wait() |
|
Page Number |
2154 |
|
Line Number |
69578 |
|
Final Accepted Text |
|
|
|
Summary |
0001363: out of date wait() RATIONALE regarding core dump indication |
|
Description |
The text:Implementations that support implementation-defined actions, such as the creation of a file containing a core image, on termination of some processes traditionally provide a bit in the status returned by wait() to indicate that such actions have occurred.
is out of date because the way to query this using WCOREDUMP() has now been added to the standard.
|
|
Desired Action |
Change:Implementations that support implementation-defined actions, such as the creation of a file containing a core image, on termination of some processes traditionally provide a bit in the status returned by wait() to indicate that such actions have occurred. to:On implementations that support the creation of a file containing a core image on some process terminations, the WCOREDUMP(stat_val) macro indicates whether creation of a core image was attempted. If it returns a non-zero value this does not necessarily mean that the core image was created, only that it was attempted. For example, if the RLIMIT_CORE limit for the process is 0, this prevents creation of the file; WCOREDUMP(stat_val) returning non-zero in this case indicates that the file would have been created if the limit had not been 0. |
| Tags |
issue8 |
|
|
Attached Files |
|
|
|
Relationships 
