-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
json parser fails to handle non-BMP unicode escapes #139
Comments
"\ud83c\uddee\ud83c\udde9" is a unicode string that represents 🇮🇩. |
Which commit are you using? I do not get this behavior on the development branch. |
@ras0219-msft I have been using the development branch. I created a repository. And it went wrong with the same error on both Linux and OS X. |
I see, thank you for the repro. I can confirm this is broken in the development branch. I have checked in a fix to the branch json-utf8-3.0. On my (Linux) machine, this fixes the issue. Could you confirm that it fixes the problem on your side as well? |
@ras0219-msft I tried json-utf8-3.0 branch, it runs correctly. But I found out a new bug and I updated the repository. Please check it. |
I am also seeing this bug. Based on the commit above we have had some success, just need to check for the the upper bounds for the high surrogate Tried with this https://github.com/minimaxir/big-list-of-naughty-strings/blob/4115c9deee71a7d732d4e50b814df33c4207789b/blns.txt#L209 |
terminate called after throwing an instance of 'std::range_error'
what(): UTF-16 string is missing low surrogate
The text was updated successfully, but these errors were encountered: