it happened.
The reason was an undefined integer in a class (uninitialized memory).
Valgrind only gives this one line warning (which is good), but
it would also be nice if it would give a backtrace for this...
Might have helped me to track down this bug sooner :)
--
With kind regards
Jonatan
\o/
With kind regards / Med vänliga hälsningar
Jonatan Wallmander
Vovoid Media Technologies AB
On 04/04/2013 11:13 PM, Philippe Waroquiers wrote:
On Tue, 2013-03-26 at 22:52 +0100, Philippe Waroquiers wrote:
The best would be to file a bug in bugzilla, for the false negative
caused by code
On 08/26/2013 10:00 AM, Mahmood Naderan wrote:
Thanks. To be honest, I didn't understand!
It seems that with these macros, I can insert them in the specific section of
the code. However my problem is different. There are iterative functions. So
I want to start valgrind after, say, 0.5 hours
