View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000785 | 1003.1(2013)/Issue7+TC1 | System Interfaces | public | 2013-11-04 15:04 | 2019-06-10 08:55 |
Reporter | geoffclare | Assigned To | |||
Priority | normal | Severity | Editorial | Type | Error |
Status | Closed | Resolution | Accepted | ||
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 |
Date Modified | Username | Field | Change |
---|---|---|---|
2013-11-04 15:04 | geoffclare | New Issue | |
2013-11-04 15:04 | geoffclare | Name | => Geoff Clare |
2013-11-04 15:04 | geoffclare | Organization | => The Open Group |
2013-11-04 15:04 | geoffclare | Section | => signal |
2013-11-04 15:04 | geoffclare | Page Number | => 1951 |
2013-11-04 15:04 | geoffclare | Line Number | => 62609 |
2013-11-04 15:04 | geoffclare | Interp Status | => --- |
2013-11-07 17:18 | Don Cragun | Status | New => Resolved |
2013-11-07 17:18 | Don Cragun | Resolution | Open => Accepted |
2013-11-07 17:18 | Don Cragun | Tag Attached: tc2-2008 | |
2019-06-10 08:55 | agadmin | Status | Resolved => Closed |