Hello,
The xml feature is really neat. Thanks for the new command line options in
3.5.0.
When --time-stamp=yes is chosen, the xml file has timestamps
for the start and finish of the process and not for individual errors.
In very long running programs time stamp for non-leak errors
is the key to
On Thu, Aug 27, 2009 at 3:51 AM, Jeff Johnsonn3...@mac.com wrote:
I'm using helgrind from 3.5.0 on OPENMP code.
I have a lazily malloc'd pthread mutex in a static global
variable that helgrind detects.
I'd like to disable the warning somehow in code, not
with a suppression, so that I can
Hi:
I tried run Valgrind without any tool on SPEC2006.
There are two benchmarks that have problem running with Valgrind.
One is 434.zeusmp, which reports failure of mmap by valgrind.
The other is 447.dealII, which does not stop after 2 days. The native
execution is only about 520 seconds.
My
On Aug 27, 2009, at 9:33 AM, Julian Seward wrote:
I'm using helgrind from 3.5.0 on OPENMP code.
I have a lazily malloc'd pthread mutex in a static global
variable that helgrind detects.
I'd like to disable the warning somehow in code, not
with a suppression, so that I can look at more
