A NOTE has been added to this issue. 
====================================================================== 
https://www.austingroupbugs.net/view.php?id=1387 
====================================================================== 
Reported By:                rhansen
Assigned To:                ajosey
====================================================================== 
Project:                    1003.1(2008)/Issue 7
Issue ID:                   1387
Category:                   System Interfaces
Type:                       Clarification Requested
Severity:                   Editorial
Priority:                   normal
Status:                     Under Review
Name:                       Richard Hansen 
Organization:                
User Reference:              
Section:                    malloc 
Page Number:                1295 (Issue 7 2018 edition) 
Line Number:                43161 (Issue 7 2018 edition) 
Interp Status:              --- 
Final Accepted Text:         
====================================================================== 
Date Submitted:             2020-08-10 16:46 UTC
Last Modified:              2020-08-11 01:08 UTC
====================================================================== 
Summary:                    Should EAGAIN be acceptable for malloc failure?
====================================================================== 

---------------------------------------------------------------------- 
 (0004918) shware_systems (reporter) - 2020-08-11 01:08
 https://www.austingroupbugs.net/view.php?id=1387#c4918 
---------------------------------------------------------------------- 
EAGAIN, if added as Don proposes, should be a may fail case, not both as
shall fail. As ENOMEM is currently synonymous with a null return with most
platforms, adding a symbolic non-NULL ptr, i.e. AGAIN_PTR, would be in
keeping with the C standard only using the return value to indicate errors.
The implementation-defined errno possible with 0 size allocs also needs
wording that it doesn't conflict with either of these, as well. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2020-08-10 16:46 rhansen        New Issue                                    
2020-08-10 16:46 rhansen        Status                   New => Under Review 
2020-08-10 16:46 rhansen        Assigned To               => ajosey          
2020-08-10 16:46 rhansen        Name                      => Richard Hansen  
2020-08-10 16:46 rhansen        Section                   => malloc          
2020-08-10 16:46 rhansen        Page Number               => 1295 (Issue 7 2018
edition)
2020-08-10 16:46 rhansen        Line Number               => 43161 (Issue 7 2018
edition)
2020-08-10 16:46 rhansen        Interp Status             => ---             
2020-08-10 17:09 rhansen        Note Added: 0004914                          
2020-08-10 17:14 rhansen        Description Updated                          
2020-08-10 17:35 rhansen        Desired Action Updated                       
2020-08-10 17:36 rhansen        Desired Action Updated                       
2020-08-10 17:39 Don Cragun     Note Added: 0004915                          
2020-08-10 17:45 alanc          Note Added: 0004916                          
2020-08-10 17:45 alanc          Note Edited: 0004916                         
2020-08-11 01:08 shware_systems Note Added: 0004918                          
======================================================================


  • [1003.1(2008... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
      • Re:... casper....@oracle.com via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group

Reply via email to