Bug #40095 | index_merge_innodb valgrind Conditional jump or move depends on uninitialized | ||
---|---|---|---|
Submitted: | 17 Oct 2008 0:16 | Modified: | 31 Oct 2008 13:27 |
Reporter: | Mark Callaghan | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server: Optimizer | Severity: | S3 (Non-critical) |
Version: | 5.0.67, 5.0, 5.1, 6.0 bzr | OS: | Any |
Assigned to: | Sergei Glukhov | CPU Architecture: | Any |
Tags: | index_merge_innodb, uninitialized, valgrind |
[17 Oct 2008 0:16]
Mark Callaghan
[17 Oct 2008 6:53]
Sveta Smirnova
Thank you for the report. Verified as described. Problem exists in version 5.1 and 6.0 too, but with different warnings. Probably separate bug should be needed for 5.1 and 6.0.
[29 Oct 2008 8:38]
Sveta Smirnova
current master.err
Attachment: bug40095.master.err (application/octet-stream, text), 16.30 KiB.
[29 Oct 2008 10:32]
Sergei Glukhov
checked(BUILD/compile-pentium-valgrind-max + mysql-test-run.pl --valgrind index_merge_innodb) latest 5.0,5.1,6.0 trees on fc9+valgrind-3.3.0, fc6+valgrind-3.2.1, can't repeat.
[29 Oct 2008 10:34]
Sveta Smirnova
Seems version of glibc matters: bug is repeatable on glibc 2.3
[31 Oct 2008 8:36]
Sveta Smirnova
Bug is not repeatable with current development sources.
[31 Oct 2008 12:51]
Mark Callaghan
I a confused. Can you reproduce this in 5.0.67 but not in the latest code available from launchpad? Can you reproduce this with older but not the latest glibc version?
[31 Oct 2008 13:27]
Mark Callaghan
I reproduce this with: valgrind 3.4, gcc 4.2, glibc 2.3.6
[31 Oct 2008 20:32]
Sveta Smirnova
I could reproduce it with 5.0.67 and a bit outdated development code, but can not with today pull.