Valgrind reports fail with unreadable debug header #19
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Valgrind reports fail with unreadable debug header
First of all, thank you for developing this incredibly useful tool! It has been very helpful.
Description
ValgrindCI fails to generate HTML reports when using Helgrind and encounters unreadable debug information for stack frames (e.g., from third-party libraries or missing debug headers (/usr/src/debug/glibc)). This results in no report being created.
Cause
The tool throws an exception when it tries to retrieve stack information from a file it can't open. This halts the entire report generation process.
Proposed Solution
Instead of failing completely, ValgrindCI should gracefully handle unreadable stack frames. It should display a message for those specific frames and continue generating the rest of the report. This provides partial but still valuable information, even in environments with incomplete debugging data.