When running 'make regtest' on an IBM POWER5 using either valgrind 3.4.1 or
3.5, the memcheck/tests/leak-cycle test fails. The bad stderr output that was
unexpected was:
leaked: 192 bytes in 12 blocks
dubious: 0 bytes in 0 blocks
reachable: 96 bytes in 6 blocks
suppressed: 0 bytes in 0 blocks
The expected output is:
leaked: 288 bytes in 12 blocks
dubious: 0 bytes in 0 blocks
reachable: 0 bytes in 6 blocks
suppressed: 0 bytes in 0 blocks
When I ran this testcase without the '-q' option, I get two leak summaries --
they are not the same. The first one is:
==20677== LEAK SUMMARY:
==20677== definitely lost: 48 bytes in 3 blocks
==20677== indirectly lost: 144 bytes in 9 blocks
==20677== possibly lost: 0 bytes in 0 blocks
==20677== still reachable: 96 bytes in 6 blocks
==20677== suppressed: 0 bytes in 0 blocks
and the second is:
==20677== LEAK SUMMARY:
==20677== definitely lost: 64 bytes in 4 blocks
==20677== indirectly lost: 224 bytes in 14 blocks
==20677== possibly lost: 0 bytes in 0 blocks
==20677== still reachable: 0 bytes in 0 blocks
==20677== suppressed: 0 bytes in 0 blocks
The second leak summary is correct.
The leak-cycle test on an Intel Xeon with Valgrind 3.5 passes. And when I run
it without the '-q' option, both leak summaries are the same; so, apparently,
the problem I'm seeing on my POWER5 system is ppc64-specific. Can anyone give
me some guidance on where to start to look for the problem?
Thanks.
-Maynard
------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
