I'm a beginner to Eclipse and C++, sorry if I'm in the wrong place or if this was already answered, I couldn't find it.
I managed to profile some easy example programs with Valgrind. At first it worked alright, but then I induced some memory errors to see how Valgrind responds. It detected them, but after fixing them I profile again and the red X indicating errors won't disappear, even though the Valgrind tab shows that Valgrind found no problems to report.
The only way to get around this is by manually deleting the problems in the problems tab, but this is very annoying
Am I forgetting to configure something? Could it be buggy?
Rerunning Valgrind on the same executable should clear the markers and then add any new ones that are caused by the new session. If this is not the case, please open a bug and provide details.
You can clear Valgrind markers from the Valgrind view by clicking on the X button in the tool-bar for that view. No rerunning of Valgrind is
required. We currently have a bug open to clear the Valgrind markers on build.