|
Viewing Issue Simple Details
[ Jump to Notes ]
|
[ Issue History ]
[ Print ]
|
|
ID |
Category |
Severity |
Type |
Date Submitted |
Last Update |
|
0000194 |
[1003.1(2008)/Issue 7] System Interfaces |
Objection |
Omission |
2009-12-10 16:48 |
2009-12-10 17:18 |
|
|
Reporter |
drepper |
View Status |
public |
|
|
Assigned To |
ajosey |
|
Priority |
normal |
Resolution |
Duplicate |
|
|
Status |
Closed |
|
|
|
|
|
Name |
Ulrich Drepper |
|
Organization |
Red Hat, Inc. |
|
User Reference |
ud-environ-async |
|
Section |
Signal Concepts |
|
Page Number |
490 |
|
Line Number |
16762 |
|
Interp Status |
--- |
|
Final Accepted Text |
|
|
|
Summary |
0000194: environ use not mentioned as async-unsafe |
|
Description |
I don't think there is anywhere a global statement that says any variable in the standard not mentioned as async-safe is automatically unsafe. Therefore I think environ should be mentioned in the context of the async-safe function table, similar to errno, just expressing the negative aspect. |
|
Desired Action |
After line 16762 add new paragraph:
Operations which obtain the value of /environ/ and operations which assign a value to /environ/ produce undefined behavior. |
| Tags |
No tags attached. |
|
|
Attached Files |
|
|
|
Relationships 
