View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001993 | 1003.1(2024)/Issue8 | System Interfaces | public | 2026-07-21 20:00 | 2026-07-21 20:00 |
| Reporter | enh | Assigned To | |||
| Priority | normal | Severity | Editorial | Type | Enhancement Request |
| Status | New | Resolution | Open | ||
| Name | Elliott Hughes | ||||
| Organization | |||||
| User Reference | |||||
| Section | pthread_create() | ||||
| Page Number | (page or range of pages) | ||||
| Line Number | (Line or range of lines) | ||||
| Interp Status | |||||
| Final Accepted Text | |||||
| Summary | 0001993: pthread_create() should allow failure with ENOMEM, not just EAGAIN | ||||
| Description | pthread_create() is currently defined to allow EAGAIN or EPERM. while _some_ resource issues fit EAGAIN, others do not warrant a retry loop. glibc and bionic both want to return ENOMEM in particular as an unretriable failure. | ||||
| Desired Action | add [ENOMEM] The system lacked the necessary resources to create another thread, and a retry is unlikely to succeed. to the errors section | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-07-21 20:00 | enh | New Issue |
