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-10 17:09 UTC
====================================================================== 
Summary:                    Should EAGAIN be acceptable for malloc failure?
====================================================================== 

---------------------------------------------------------------------- 
 (0004914) rhansen (manager) - 2020-08-10 17:09
 https://www.austingroupbugs.net/view.php?id=1387#c4914 
---------------------------------------------------------------------- 
A problem arises if we were to replace all instances of [ENOMEM] with
[ENOMEM], [EAGAIN]: Some functions already specify [EAGAIN] for other error
conditions. These
include:<ul><li>accept</li><li>fclose</li><li>fflush</li><li>fgetc</li><li>fgetwc</li><li>fork</li><li>fputc</li><li>fputwc</li><li>mlock</li><li>mlockall</li><li>mmap</li><li>mprotect</li><li>open</li><li>openat</li><li>posix_trace_create</li><li>posix_trace_create_withlog</li><li>pread</li><li>pthread_barrier_init</li><li>pthread_cond_init</li><li>pthread_key_create</li><li>pthread_mutex_init</li><li>pthread_rwlock_init</li><li>pthread_rwlockattr_init</li><li>pthread_spin_init</li><li>read</li><li>recv</li><li>recvfrom</li><li>recvmsg</li><li>sendmsg</li><li>sendto</li></ul>


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                          
======================================================================


  • [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

Reply via email to