-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Warnings thrown by Coverity static analyses #4030
Comments
For the very first one it says |
Thanks for the quick assessment. The information is from: https://scan.coverity.com/projects/2860 Regarding the first message ( CID 434544) the only little information I further see is:
There is some extra information:
I´ve not checked he path through ch the static analyzer comes to this conclusion. I´ll have a look at it next week. Regarding the second problem (CID 534540) I see some extra information:
|
All of NEGATIVE_RETURNS look like false positives because the return type of Line 433 in 18a9676
You might want to report an issue to Coverity since it's clearly broken on their part, e.g.
is obviously nonsensical since an unsigned value cannot be negative. Filtering those out this leaves 7 reports which I haven't looked at yet:
|
UNCAUGHT_EXCEPT is also a false positive - |
BAD_SHIFT are also false positive that contradict the asserts. This leaves the following 3 reports:
|
I added a test for the full exponent range and unsurprisingly the last warnings also turned out to be false positives. |
Doxygen uses spdlib and recently updated the version of spdlib. The used version of spdlib again has fmtlib 10.2.1 bundled into it .
Coverity scan throws a number of warnings about this version:
I think these warnings should be evaluated and probably be fixed.
The text was updated successfully, but these errors were encountered: