View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
00001941003.1(2008)/Issue 7System Interfacespublic2009-12-10 16:482009-12-10 17:18
Reporterdrepper Assigned Toajosey  
PrioritynormalSeverityObjectionTypeOmission
Status ClosedResolutionDuplicate 
NameUlrich Drepper
OrganizationRed Hat, Inc.
User Referenceud-environ-async
SectionSignal Concepts
Page Number490
Line Number16762
Interp Status---
Final Accepted Text
Summary0000194: environ use not mentioned as async-unsafe
DescriptionI 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 ActionAfter line 16762 add new paragraph:

Operations which obtain the value of /environ/ and operations which assign a value to /environ/ produce undefined behavior.
TagsNo tags attached.

Relationships

duplicate of 0000066 Closedajosey sigaction/signal lists are different 

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2009-12-10 16:48 drepper New Issue
2009-12-10 16:48 drepper Status New => Under Review
2009-12-10 16:48 drepper Assigned To => ajosey
2009-12-10 16:48 drepper Name => Ulrich Drepper
2009-12-10 16:48 drepper Organization => Red Hat, Inc.
2009-12-10 16:48 drepper User Reference => ud-environ-async
2009-12-10 16:48 drepper Section => Signal Concepts
2009-12-10 16:48 drepper Page Number => 490
2009-12-10 16:48 drepper Line Number => 16762
2009-12-10 17:17 msbrown Relationship added duplicate of 0000066
2009-12-10 17:18 msbrown Interp Status => ---
2009-12-10 17:18 msbrown Status Under Review => Closed
2009-12-10 17:18 msbrown Resolution Open => Duplicate