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
6 new issues identified by coverity #755
Comments
@EmericBr I'd like you to have a look at these as I suspect at least some of them are real bugs. |
|
|
Yes, |
Ah, indeed. I missed that one.
Coverity should probably be teached that this kills the process. @chipitsine Do you know whether some define can be used to check for coverity? Then the definition could possibly be adjusted to something like:
|
we run coverity using our own build process. coverity does not know nothing about it, I'd give 100% that it does not define any macros (because we start build process) but we can add define to our coverity scan |
I think, we can try coverity modeling. I'll have a look |
@TimWolla , what do you think, if we pass |
I guess that should work, yes. Make sure to take care of the |
I've marked issues in Coverity. |
it works if I use SILENT_DEFINE
it fails with just DEFINE
I'll try to fix DEFINE escaping. if I won't be lucky, I'll send patch with SILENT_DEFINE |
Hi Ilya, I suggest that you don't waste your time trying to fix DEFINE escaping. I gave up years ago, it involves escaping for shell, makefile and C at the same time. The further you go, the more it requires the user to be extra careful and that was not worth it. Just use SILENT_DEFINE for this, that's perfectly fine. Just my two cents ;-) |
By the way, you can do something simpler, along what Tim proposed above. Instead of testing for COVERITY, test for DEBUG_USE_ABORT and set this variable in the DEBUG one at build time. Do not forget to mention it in the makefile where other ones are enumerated. No need to go into details, those using DEBUG are responsible for knowing the consequences, hence reading the code. |
changes applied in d344910 closing this issue |
please let me known which of them are false positive
The text was updated successfully, but these errors were encountered: