bcoconni/ValgrindCI

Detecting debug info

Opened this issue · 2 comments

Basically just a feature request I came up with after using this module for some time.

I am using a cmake based project, many times I wonder why I do not get any errors reported in html's generated by ValgrindCI, even though pure valgrind reports memory leaks. Reason is simply I forgot to compile with debug info / debug mode again.

It would be nice if ValgrindCI could warn the user that there is no debug / line info, so output wont be correct.

Hi @Stadik, do you mean that ValgrindCI should raise an error if the XML file generated contains no info ? If so, I guess we should make sure that ValgrindCI is capable of making the distinction between a genuinely error free project and a project that did not trigger debug info generation. If indeed Valgrind generates different XML files for these 2 scenarios then I guess that your request is feasible.

Basically valgrind writes content into XML under both release and debug builds.

But when generating html report or summary via ValgrindCI, it is correct for dbeug builds and shows 0 errors for release builds.
Number of errors seems correct in both cases.

Here the two xml files (I upload it as txt because of github)
output-release.txt
output-debug.txt

So as you noted down, best would be if it detects missing debug info, since currently outcome will be the same for real case without any errors and simple release builds. (which is an issue for e.g. CICD valgrind test stage)