-
Notifications
You must be signed in to change notification settings - Fork 363
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
CxxValgrindSensor: allow multiple <stack> nodes #1440
* proper parsing of multiple <stack>s and <auxwhat>s see https://github.com/pathscale/valgrind-mmt/blob/master/docs/internals/xml-output.txt Each stackstrace of Valgrind will be stored as a separate NewIssue. The reason is missing formatting for error messages (even line breaks are not allowed). Error messages with one stack trace are already hard to read. * revisit Valgrind*::equals() and Valgrind*::hashCode() implementation a. equals() shouldn not be implemented through hashCode() because there could be hash collisions and unequal objects could return true b. perform equals()/hashCode() over all fields I believe that SonarQube has to show the Valgrind's report as-is. There should be no filtering or obfuscation
- Loading branch information
1 parent
14089b8
commit 663e698
Showing
11 changed files
with
502 additions
and
100 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.