Bug #560 mysqld catch signal 11 and core dump

• Submitted: 31 May 2003 21:33
• Modified: 2 Jun 2003 6:04
• Reporter: shilling lee
• Status: Duplicate
• Category: MySQL Server: MyISAM storage engine
• Severity: S1 (Critical)
• Version: 4.0.13
• OS: Linux (RedHat Linux 8.0)
• CPU Architecture: Any

[31 May 2003 21:33] shilling lee

Description:
mysqld catch signal 11 and dumps core when dumping table

mysqld dumps when processing this kind of request

=== cut from grep ===
mysqld.log:thd->query at 0x8a32e50 = /*!40000 ALTER TABLE smo_trace_20030601 ENABLE KEYS */
mysqld.log:thd->query at 0x88ab4b0 = /*!40000 ALTER TABLE proc_trace_20030601 ENABLE KEYS */
mysqld.log:thd->query at 0x88237d0 = /*!40000 ALTER TABLE smt_trace_20030601 ENABLE KEYS */
mysqld.log:thd->query at 0x889d290 = /*!40000 ALTER TABLE termregion ENABLE KEYS */
mysqld.log:thd->query at 0x88263d0 = /*!40000 ALTER TABLE subscribe ENABLE KEYS */
mysqld.log:thd->query at 0x88a1138 = /*!40000 ALTER TABLE jiaoyou ENABLE KEYS */
=== cut ends ===

I use this binary package "mysql-standard-4.0.13-pc-linux-i686.tar.gz"
My OS type is RedHat 8.0 "Linux stat 2.4.18-14 #1 Wed Sep 4 13:35:50 EDT 2002 i686 i686 i386 GNU/Linux"

How to repeat:
import a sql file that contains the line like:

/*!40000 ALTER TABLE smo_trace_20030601 ENABLE KEYS */

Suggested fix:
do not import this kind of sql file ?

[1 Jun 2003 8:57] Garrett Stuck

The following sequence of commands consistently crashes the mysqld-nt.exe server in version 4.0.13.  

use test;
drop table if exists tmp;
create table tmp (id tinyint primary key not null);
lock tables tmp write;
insert into tmp values (1);
alter table tmp enable keys;
select * from tmp;

[2 Jun 2003 6:04] MySQL Verification Team

Same as #478, which is already fixed in BK 4.0 tree.