Windows: Fix rare argument parsing bug #680
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This is insane |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #679. See explanation in the code comments. The bug comes from Qt's code here and here. I borrowed this for the fix, which is how Qt does it if it doesn't detect "modified" arguments.
Initially I tried simply setting
argc = __argcandargv = __argvat the top ofmain, which worked great on the 64-bit Qt 6 build, but it crashed the 32-bit Qt 5 build if the weird unicode character was involved.EDIT: I reported this as QTBUG-125380, by the way.