Anonymous | Login | 2024-04-29 15:17 UTC |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||
ID | Category | Severity | Type | Date Submitted | Last Update | ||
0000785 | [1003.1(2013)/Issue7+TC1] System Interfaces | Editorial | Error | 2013-11-04 15:04 | 2019-06-10 08:55 | ||
Reporter | geoffclare | View Status | public | ||||
Assigned To | |||||||
Priority | normal | Resolution | Accepted | ||||
Status | Closed | ||||||
Name | Geoff Clare | ||||||
Organization | The Open Group | ||||||
User Reference | |||||||
Section | signal | ||||||
Page Number | 1951 | ||||||
Line Number | 62609 | ||||||
Interp Status | --- | ||||||
Final Accepted Text | |||||||
Summary | 0000785: Left-over text about signal() in a multi-threaded process | ||||||
Description |
According to XSH 2.9.1 Thread-Safety, signal() is thread-safe, and the signal() page says: "If the process is multi-threaded, [...] the behavior is undefined if the signal handler [does various things]." which implies that the behaviour is well defined if the signal handler does not do those things. However, the reference to multi-threaded processes here was added in TC1 and it appears that the need to remove the 2nd paragraph ("Use of this function is unspecified in a multi-threaded process") at the same time was overlooked. |
||||||
Desired Action |
Delete the paragraph: Use of this function is unspecified in a multi-threaded process. |
||||||
Tags | tc2-2008 | ||||||
Attached Files | |||||||
|
There are no notes attached to this issue. |
Mantis 1.1.6[^] Copyright © 2000 - 2008 Mantis Group |