Thank you very much for considering this issue.
Some of the rules in question, for C language analysis, are those with the recommandation messages listed below.
I had to work from the issues list copy/paste output so don’t have the corresponding rules id.
But this helped me discovering one important potential cause of these issues marking as new: their lines number are wrong !!!
They are actually all out of the associated files number of lines:
L2591 for a file of 291 lines
L553 for a file of 42 lines
This applies to both C and CPP files.
As the line number is documented as part of the issues recognition from one build to another, my updated question is: in what circumptances can the sonarqube analyzers of server fail in reading issues line numbers ?
Notice that I need to concentrate on occurences of that problem related to the C language, as it corresponds to the most frequent and critical context for me.
Also I insist on the fact that the problem can occur when none of the related code (by far) has been modified. For instance memory allocation issues cannot be raised by any code change the whole modules related to these memory allocations were left untouched.
Here are some of the issues rules label as appearing on the issues lists tab:
(cpp) Review the data-flow; this memory allocation might not have been released when going out of scope.
(cpp) Remove the unary minus operator or change the expression’s underlying type.
(cpp) Catch the exception by reference.
(cpp) Remove this unreachable statement.
( c ) Change this condition so that it does not always evaluate to “true”; some subsequent code is never executed.
( c ) Review this data-flow; “shdr” is dereferenced and may be null.
( c ) Remove this unreachable statement.
Thanks in advance