Valgrind: Conditional jump or move depends on uninitialised value(s) in ibuf_delete_rec
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
Expired
|
High
|
Unassigned | ||
5.1 |
Won't Fix
|
Undecided
|
Unassigned | ||
5.5 |
Expired
|
Undecided
|
Unassigned | ||
5.6 |
Expired
|
High
|
Unassigned |
Bug Description
==20130== Thread 6:
==20130== Conditional jump or move depends on uninitialised value(s)
==20130== at 0xBE9EDB: ibuf_delete_
==20130== by 0xBEAD79: ibuf_merge_
==20130== by 0xD83B5A: buf_page_
==20130== by 0xDF0E2A: fil_aio_
==20130== by 0xCF73D9: io_handler_thread (srv0start.cc:477)
==20130== by 0x4E36850: start_thread (in /lib64/
==20130== by 0x611890C: clone (in /lib64/
==20130==
Looks like it may have been on this query;
2013-08-05T15:48:20 [20169] Query: DELETE FROM `table1000_
tags: | added: 56qual |
It is probably upstream, but way too little information too analyze. A setup where MySQL is crashed on the 1st Valgrind error probably would help.
Roel, please consider adding --track-origins=yes to Valgrind options too.