|
From: Julian S. <js...@ac...> - 2012-01-27 09:16:45
|
> My another guess is that the corruption can be caused by some memory > allocation routines we do not wrap, which mess up with Valgrind's > allocations. One way you can generally simplify the scenario is to run with --tool=none and see if it still fails. This removes all memcheck style instrumentation and removes all malloc etc function intercepting; basically runs the program on the framework with no instrumentation. J |