On Mon, Jul 18, 2022 at 03:49:11PM +0000, Austin Group Bug Tracker via austin-group-l at The Open Group wrote: > > The following issue has been RESOLVED. > ====================================================================== > https://austingroupbugs.net/view.php?id=1219 > ====================================================================== > Reported By: sebor > Assigned To: ajosey > ====================================================================== > Project: 1003.1(2008)/Issue 7 > Issue ID: 1219 > Category: System Interfaces > Type: Error > Severity: Objection > Priority: normal > Status: Resolved > Name: Martin Sebor > Organization: > User Reference: > Section: snprintf > Page Number: 906 > Line Number: 30447 > Interp Status: --- > Final Accepted Text: > Resolution: Accepted As Marked > Fixed in Version: > ====================================================================== > Date Submitted: 2018-12-12 17:29 UTC > Last Modified: 2022-07-18 15:49 UTC > ====================================================================== > Summary: snprintf reequirement to fail when n > INT_MAX > conflicts with C > ====================================================================== > Relationships ID Summary > ---------------------------------------------------------------------- > related to 0000761 Requirement of error for snprintf with ... > ====================================================================== > > ---------------------------------------------------------------------- > (0005895) Don Cragun (manager) - 2022-07-18 15:49 > https://austingroupbugs.net/view.php?id=1219#c5895 > ---------------------------------------------------------------------- > Delete lines 30917-30918 in D2.1 (page 904). > > Change page 990 line 33924 in D2.1 from:<blockquote>The value of <i>n</i> > is greater than {INT_MAX}.</blockquote>to:<blockquote>The number of wide > characters requested to be written was <i>n</i> or more.</blockquote> > > Issue History > Date Modified Username Field Change > ====================================================================== > 2018-12-12 17:29 sebor New Issue > 2018-12-12 17:29 sebor Status New => Under Review > 2018-12-12 17:29 sebor Assigned To => ajosey > 2018-12-12 17:29 sebor Name => Martin Sebor > 2018-12-12 17:29 sebor Section => snprintf > 2018-12-12 17:29 sebor Page Number => 906 > 2018-12-12 17:29 sebor Line Number => 30447 > 2018-12-12 17:48 sebor Note Added: 0004182 > 2018-12-12 20:29 sebor Note Added: 0004183 > 2018-12-12 21:06 eblake Relationship added related to 0000761 > 2022-07-18 15:49 Don Cragun Interp Status => --- > 2022-07-18 15:49 Don Cragun Note Added: 0005895 > 2022-07-18 15:49 Don Cragun Status Under Review => > Resolved > 2022-07-18 15:49 Don Cragun Resolution Open => Accepted As > Marked > ====================================================================== >
I went to apply the resolution of this issue to musl libc and noticed that the corresponding issue in swprintf was never brought up or addressed. Should I open a new issue for it or can it be fixed along with this? Rich
