Is SonarQube capable of showing the steps taken that resulted in the issue/rule violation (i.e. which “path” in the code was taken to get to the issue)? For example, the Clang Static Analyzer highlights the lines in the source file where, say, “1. var1 initialized to a null pointer value,” “2. taking false branch,” “3. taking true branch,” … “7. access from var1 results in a null pointer dereference.” Is there a way in SonarQube to find similar info about the steps taken within the code that found the issue(s)?
I am using SonarQube Developer Edition v. 7.2.1, Sonar Scanner v. 4.3.0. Is showing steps something included in newer versions of SonarQube?