Unexpected behaviour of cfamily scanner results

[ganncamp (G Ann Campbell)]

Hi,

Welcome to the community!

This thread explains why that’s the expected behavior:

Sonar missed catching null pointer accesses

Trying to check if sonar is able to catch some obvious bad code. Wrote following sample bad code: 18 char *ptr1 = NULL; 19 char *ptr2 = NULL; 20 char *temp = NULL; 21 char line[] = "testingwithoutcoloninline"; 22 if (!bitmap_max_entries) { 23 temp = strpbrk(line, ";"); 24 *temp = '\0'; 25 *ptr1 = 'a'; 26 *ptr2 = 'a'; 27 test_func(ptr2); 28 } It is analyzing…

 
Ann