This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
1st scenario; - create C++ project with such code: int main(int argc, char** argv) { int i = 1/0; int a[2]; a[4] = 1; return 0; } - call Options window - select Editor > Hints > C/C++ - switch off all Clank hints - switch on 'core.VLASize' hint - press OK button - close file, open file again ==> I see both Clank hints. Expected result: 0 hints.
2nd scenario; - create C++ project with such code: int main(int argc, char** argv) { int i = 1/0; int a[2]; a[4] = 1; return 0; } - call Options window - select Editor > Hints > C/C++ - switch off all Clank hints - switch on 'core.DivideZero' hint - Select 'Error' type in "Show As" listbox - press OK button - close file, open file again ==> I see 2 warnings. Expected result: 1 error.
Invalid. works as expected. clang works the same way for the given example. To check use attached file. 1. Turn off all except "unix.Malloc" -> you will see 6 warning 2. Turn on "core" -> 9 warnings
Created attachment 164969 [details] coverage.c sample file
(In reply to Maria Tishkova from comment #2) > 1. Turn off all except "unix.Malloc" -> you will see 6 warning true > 2. Turn on "core" -> 9 warnings true Turn on all hints -> no warnings
also alpha.valist checker breaks other checkers 3rd scenario: - Switch on all Clank hints - Open coverage.c file ==> no any warnings!!! - Switch off alpha.valist hint ==> a lot of warnings
(In reply to soldatov from comment #5) > also alpha.valist checker breaks other checkers > > 3rd scenario: > - Switch on all Clank hints > - Open coverage.c file > ==> no any warnings!!! > - Switch off alpha.valist hint > ==> a lot of warnings The behavior is the same as clang has. it is not clear what to do in such cases. there are unit tests in clang that checks that 3 checkers will produce less errors..