Make Nanos++ more Valgrind-friendly
Nanos++ uses several idioms that fool Valgrind. The worst offender is the stack switch message, but we will not address it here.
The remaining warnings deal about mismatches between new/new[]
and delete/delete[]
We can really take two options:
- Create a Valgrind suppression file (this assumes we are very smart and now better than Valgrind itself, which sometimes may be true ;)
- Fix the mismatching occurrences. Note that I'm not stating that the current code is wrong. It just triggers lots of confusing warnings that may overwhelm a Valgrind user.
I am attaching some patches for review.