Bug #24533 | uninited null_bit of m_after_image | ||
---|---|---|---|
Submitted: | 23 Nov 2006 7:09 | Modified: | 27 Nov 2006 18:46 |
Reporter: | Andrei Elkin | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Row Based Replication ( RBR ) | Severity: | S2 (Serious) |
Version: | 5.1.14 | OS: | |
Assigned to: | Mats Kindahl | CPU Architecture: | Any |
[23 Nov 2006 7:09]
Andrei Elkin
[23 Nov 2006 9:15]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/15749 ChangeSet@1.2371, 2006-11-23 10:15:02+01:00, mats@romeo.(none) +1 -0 BUG#24533 (uninitialized null but of m_after_image): Patch to fix valgrind warning that uninitialized bytes were written. The warning was caused by set_default(), which assumes that the field pointer is pointing into record[0], while all other functions honors the move_field_offset().
[23 Nov 2006 9:44]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/15750 ChangeSet@1.2372, 2006-11-23 10:43:43+01:00, mats@romeo.(none) +1 -0 BUG#24533 (uninitialized null bits in m_after_image): Removing valgrind memory checks from code.
[27 Nov 2006 18:46]
Paul DuBois
Noted in 5.1.14 changelog. Some unnecessary Valgrind warnings were removed from the server.