bcoconni
Valgrind reports fail with unreadable debug header
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.
