Bug #20578 | memory bug (valgrind) in sctype_latin1 , ysdate_is_now, rpl_insert_ignore | ||
---|---|---|---|
Submitted: | 20 Jun 2006 16:03 | Modified: | 21 Jun 2006 13:32 |
Reporter: | Andrei Elkin | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S1 (Critical) |
Version: | 5.0.23 | OS: | Linux (RHAS3 EM64T Valgrind) |
Assigned to: | Kristian Nielsen | CPU Architecture: | Any |
[20 Jun 2006 16:03]
Andrei Elkin
[20 Jun 2006 16:24]
Andrei Elkin
also rpl000017.
[21 Jun 2006 7:43]
Kristian Nielsen
I just discovered that Monty added a suppression for this in 5.1. I will backport the suppression to 5.0 to remove the Valgrind error report. Note that this bug is difficult to reproduce (and hence difficult to check if fixed), since it depends on a race condition.
[21 Jun 2006 9:23]
Andrei Elkin
I am certain, "almost", this one does nothing to replication for both testcases and the stack itself. STACK: at 0x4A1A122: calloc (vg_replace_malloc.c:279) by 0x940AF9: my_thread_init (my_thr_init.c:170) by 0x5A9838: kill_server_thread (mysqld.cc:1022) by 0x4D51C63: start_thread
[21 Jun 2006 10:56]
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/8007
[21 Jun 2006 13:32]
Kristian Nielsen
Suppression for this Valgrind error pushed to mysql-5.0. No changelog entry needed, since this is only silencing a Valgrind warning that is not the symptom of a real bug.