Bug #12193 Valgrind: Conditional jump or move depends on uninitialised value(s)
Submitted: 27 Jul 2005 4:24 Modified: 26 Aug 2005 1:28
Reporter: Matt Wagner Email Updates:
Status: Can't repeat Impact on me:
Category:MySQL Server Severity:S3 (Non-critical)
Version:4.1.12 OS:x86 linux 32bit
Assigned to: Jim Winstead CPU Architecture:Any

[27 Jul 2005 4:24] Matt Wagner
I've been working with Guilhem to run valgrind on a special compile of MySQL Cluster 4.1.12. I've found numerous reports of "Conditional jump or move depends on uninitialised value(s)" in the following tests:

 - dirty_close
 - func_compress
 - func_default
 - rpl_optimize
 - rpl_rewrite_db

Guilhem tells me that these are significant because, "an if() condition may randomly be true or false, thus causing impredictable behaviour."

How to repeat:
Run ./mysql-test-run --valgrind-all on special debug copy of mysql-cluster (ask Matt in ENG where to find).
[26 Aug 2005 1:28] Jim Winstead
if i run ./mysql-test-run --valgrind-all <tests> in mysqldev@production:~/my/valgrind/mysql-4.1.12-valgrind-build/test/mysql/mysql-test, there are just a couple of (apparently) bogus warnings in var/log/warnings.

i also don't know what "special compile" means.

i need more exact steps to repeat.