Description:
Test case:
CREATE TABLE `tApplicationlog_copy` (
`ID` int(10) unsigned NOT NULL auto_increment,
`CREATETIME` datetime default NULL,
PRIMARY KEY (`ID`)
) ENGINE=MyISAM;
CREATE TABLE `tApplicationperform_copy` (
`ID` int(10) unsigned NOT NULL auto_increment,
`CREATETIME` datetime default NULL,
PRIMARY KEY (`ID`)
) ENGINE=MyISAM;
And then:
----------
SELECT DATE(CREATETIME) FROM tApplicationlog_copy
UNION
SELECT DATE(CREATETIME) FROM tApplicationperform_copy;
----------
causes crash:
----------
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.
key_buffer_size=402653184
read_buffer_size=2093056
max_used_connections=4
max_connections=200
threads_connected=4
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1211614 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x85d5a18
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=0xbff5ec48, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x808b193
0x82deab8
0x80866ca
0x8082bb7
0x80c3728
0x80bcc41
0x80bdf22
0x812a363
0x8128980
0x80baebc
0x809ae3a
0x809f4d9
0x8099a68
0x8099438
0x8098b07
0x82dc26c
0x8305bfa
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 0x861f870 = SELECT DATE(CREATETIME) FROM tApplicationlog_copy UNION SELECT DATE(CREATETIME) FROM tApplicationperform_copy
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
050330 00:41:38 mysqld restarted
----------
Verified with three independent 4.1.10(a) installations. Works okey with 4.1.7a.
How to repeat:
see above
Suggested fix:
Temporary fix: downgrade. Not sure if this is duplicate of bug #8660 (?)
