| Summary: | Found nondeterminism in Valgrind's BBV logs | ||
|---|---|---|---|
| Product: | [Developer tools] valgrind | Reporter: | jo.alen1 <jo.alen1> |
| Component: | bbv | Assignee: | Vince Weaver <vince> |
| Status: | REPORTED --- | ||
| Severity: | normal | CC: | pjfloyd |
| Priority: | NOR | ||
| Version First Reported In: | 3.18.1 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| See Also: |
https://bugs.kde.org/show_bug.cgi?id=492388 https://bugs.kde.org/show_bug.cgi?id=492343 https://bugs.kde.org/show_bug.cgi?id=492382 https://bugs.kde.org/show_bug.cgi?id=492348 https://bugs.kde.org/show_bug.cgi?id=492389 |
||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Red represents removals while green represents additions. This is a screenshot of two Valgrind BBV logs for the same executable and configurations ran for two runs. | ||
I don’t think anyone is maintaining BBV so don’t expect a quick response. (In reply to Paul Floyd from comment #1) > I don’t think anyone is maintaining BBV so don’t expect a quick response. No worries! Anything helps from the Valgrind team!! |
Created attachment 173111 [details] Red represents removals while green represents additions. This is a screenshot of two Valgrind BBV logs for the same executable and configurations ran for two runs. Hi Valgrind Maintainers and Team! I have been using Valgrind as a tool to check for nondeterministic behaviors and I know that there are multiple subtools that Valgrind's suite comes with. I would like to inquire about the BBV subtool in analyzing some of the reports generated after each run against a binary. This nondeterminism concerns the Valgrind-generated log as a result of running BBV on a binary. Our test concluded that there was nondeterministic reporting in 37/41 repositories. Would the team look into this matter and remedy the issue or provide a potential explanation for this? Thank you!! STEPS TO REPRODUCE 1. Use a GitHub Actions runner with Ubuntu 22.04 + Valgrind 3.18.1 pulled from the Ubuntu package manager 2. Run your executable with exp-bbv enabled. 3. Obtain the Valgrind reports OBSERVED RESULT Specifically, we noticed that the common category of these apparent flakiness comes from Valgrind's performance metrics summaries (i.e - total instruction counts and total/unique reps). The attached screenshot shows in red of missing versus green of additions.