Description:
Verion MysqlServer: 4.1.10a-Max
On query:
(Select now())
UNION
(SELECT now() + interval 3 month);
Error:
Error Code : 2013
Lost connection to MySQL server during query
(438 ms taken)
Error log:
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x8a14a58 = (Select now())^M
UNION^M
(SELECT now() + interval 3 month)
thd->thread_id=1
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.
Number of processes running now: 0
070117 10:47:52 mysqld restarted
070117 10:47:53 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
070117 10:47:53 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 2327378.
InnoDB: Doing recovery: scanned up to log sequence number 0 2327378
070117 10:47:53 InnoDB: Flushing modified pages from the buffer pool...
070117 10:47:53 InnoDB: Started; log sequence number 0 2327378
/usr/sbin/mysqld-max: ready for connections.
Version: '4.1.10a-Max' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Edition - Max (GPL)
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
key_buffer_size=8388600
read_buffer_size=131072
max_used_connections=1
max_connections=100
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225791 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x8a1af40
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
Cannot determine thread, fp=0x41d60c54, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x8138b57
0x400518f8
0x8169cda
0x817557a
0x816c0da
0x816c5a2
0x81e6523
0x81e4b10
0x816967c
0x814929a
0x814d999
0x8147e88
0x8147854
0x8146f07
0x4004c484
0x420df147
How to repeat:
Every run query.
