[MinGW-Notify] [mingw] #39687: wcsrtombs with NULL dest pointer doesn't ignore len parameter

Zurück zum Archiv-Index
MinGW Notification List mingw****@lists*****
Mon Mar 16 21:50:13 JST 2020


#39687: wcsrtombs with NULL dest pointer doesn't ignore len parameter

  Open Date: 2019-10-19 17:38
Last Update: 2020-03-16 12:50

URL for this Ticket:
    https://osdn.net//projects/mingw/ticket/39687
RSS feed for this Ticket:
    https://osdn.net/ticket/ticket_rss.php?group_id=3917&tid=39687

---------------------------------------------------------------------

Last Changes/Comment on this Ticket:
2020-03-16 12:50 Updated by: keith

Comment:

An oversight in the mingwrt-5.3 implementation of mbrtowc(), if the caller
fails to check for return of a high surrogate, and correctly follow up by
retrieving the complementary low surrogate, allows the pending surrogate pair
conversion state to be incorrectly interpreted, on a following mbrtowc() call,
as a new MBCS sequence instead of as a low surrogate awaiting retrieval. This
is now corrected, in the repository, and will thus be corrected in
mingwrt-5.3.1.

A similar defect, whereby pending conversion state could be misinterpreted as
an already complete MBCS sequence, in the (perhaps less likely) event that the
active codeset is changed between mbrtowc() calls, has also been corrected.



---------------------------------------------------------------------
Ticket Status:

      Reporter: gallickgunner
         Owner: keith
          Type: Issues
        Status: Open [Owner assigned]
      Priority: 5 - Medium
     MileStone: (None)
     Component: WSL
      Severity: 5 - Medium
    Resolution: None
---------------------------------------------------------------------

Ticket details:

I'm using MinGW-gcc-6.3.0. The wcsrtombs() function as mentioned in the docs on
cppreference should return the number of bytes that would have been written to
src. However it doesn't do so on my end. It seems the implementation doesn't
ignore the length parameter when dest is passed as NULL? A similar issue was
reported and presumably fixed for the Mingw-w64 on the sourceforge site
Currently working around by passing INT_MAX as the length parameter, so it
finishes within the limit and returns the size.

I apologize in advance if this is just an issue from my end or if any other
info is missing. First time submitting a ticket :)



-- 
Ticket information of MinGW - Minimalist GNU for Windows project
MinGW - Minimalist GNU for Windows Project is hosted on OSDN

Project URL: https://osdn.net/projects/mingw/
OSDN: https://osdn.net

URL for this Ticket:
    https://osdn.net/projects/mingw/ticket/39687
RSS feed for this Ticket:
    https://osdn.net/ticket/ticket_rss.php?group_id=3917&tid=39687



More information about the MinGW-Notify mailing list
Zurück zum Archiv-Index