Errors reported by valgrind

Martti Kuparinen martti.kuparinen@REDACTED
Fri Feb 19 08:33:40 CET 2010


I'm using 64-bit Ubuntu 9.10 and I downloaded R13B03 and compiled it with

CFLAGS="-g" LDFLAGS="-g" ./configure --prefix=/tmp/otp13b3 --enable-threads 
--enable-smp-support --enable-kernel-poll --enable-hipe 
--enable-megaco-flex-scanner-lineno --enable-megaco-reentrant-flex-scanner 

Next I wanted to see what valgrind 3.5.0 thinks so I executed

cd bin/x86_64-unknown-linux-gnu
export BINDIR=`pwd`

valgrind --trace-children=yes --verbose --leak-check=full \
          --show-reachable=yes --track-origins=yes --malloc-fill=AB \
          --free-fill=CD \

==24653== LEAK SUMMARY:
==24653==    definitely lost: 57,344 bytes in 7 blocks
==24653==    indirectly lost: 0 bytes in 0 blocks
==24653==      possibly lost: 2,108,608 bytes in 15 blocks
==24653==    still reachable: 9,001,366 bytes in 89 blocks
==24653==         suppressed: 0 bytes in 0 blocks
==24653== ERROR SUMMARY: 9 errors from 9 contexts (suppressed: 4 from 4)

I also executed

valgrind --trace-children=yes --verbose --tool=helgrind \

==24733== ERROR SUMMARY: 754 errors from 97 contexts (suppressed: 13211 from 190)

Most of those were "Possible data race during write of size X" and "Thread #X: 
lock order ... violated" kind of errors.

Anyone else getting similar results? Should I file a problem report (where?) or 
is this mail enough?


More information about the erlang-questions mailing list