-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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
Issue 13589: tesseract-ocr/fuzzer-api: Undefined-shift in IntegerMatcher::UpdateTablesForFeature #2297
Milestone
Comments
stweil
changed the title
Undefined-shift · IntegerMatcher::UpdateTablesForFeature
Issue 13589: tesseract-ocr/fuzzer-api: Undefined-shift in IntegerMatcher::UpdateTablesForFeature
Mar 8, 2019
stweil
added a commit
to stweil/tesseract
that referenced
this issue
Mar 11, 2019
Shift operations are undefined for negative numbers, but at least on Intel they return the same value as a multiplication with 2 ^ shift value. This fixes runtime errors reported by sanitizers and OSS-Fuzz: intmatcher.cpp:821:59: runtime error: left shift of negative value -14 intmatcher.cpp:823:75: runtime error: left shift of negative value -512 intmatcher.cpp:820:50: runtime error: left shift of negative value -80 See issue tesseract-ocr#2297 and https://oss-fuzz.com/testcase-detail/4845195990925312 for details. Signed-off-by: Stefan Weil <sw@weilnetz.de>
This issue is addressed in pull request #2309. |
stweil
added a commit
to stweil/tesseract
that referenced
this issue
Mar 12, 2019
Shift operations are undefined for negative numbers, but at least on Intel they return the same value as a multiplication with 2 ^ shift value. This fixes runtime errors reported by sanitizers and OSS-Fuzz: intmatcher.cpp:821:59: runtime error: left shift of negative value -14 intmatcher.cpp:823:75: runtime error: left shift of negative value -512 intmatcher.cpp:820:50: runtime error: left shift of negative value -80 See issue tesseract-ocr#2297 and https://oss-fuzz.com/testcase-detail/4845195990925312 for details. Signed-off-by: Stefan Weil <sw@weilnetz.de>
Is this fixed? |
This issue is fixed, see https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=13589. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue reported by OSS Fuzz:
The same issue is also reported when code is built with GCC sanitizers (for example when running the
stringrenderer_test
), see Wiki for build instructions.The text was updated successfully, but these errors were encountered: