Bug #70524 Loading binary log for point-in-time recovery kills connection w/signal 11 error
Submitted: 4 Oct 2013 16:32 Modified: 29 Mar 2016 0:24
Reporter: Roger Hill Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:7.2.12 OS:Linux (CentOS 6.4)
Assigned to: MySQL Verification Team CPU Architecture:Any

[4 Oct 2013 16:32] Roger Hill
Description:
While tasting point-in-time recovery, a certain query generates error:

ERROR 2013 (HY000): Lost connection to MySQL server during query
--------------
SET TIMESTAMP=1380268799
--------------

ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/tmp/mysql.sock' (111)
ERROR:
Can't connect to the server

with the following in the mysqld log:

19:16:02 UTC - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail

I am uploading the binary log file, the sql file generated by the mysqlbinlog that is being loaded,(one without the verbose option and one with the verbose option), a log of the loading errors (one using a socket connection and one using a tcp connection), the mysqld log, a text file showing the memory usage.

How to repeat:
I can repeat this by loading the backup and then reloading the binary logs.  

Suggested fix:
Not sure.