Bug #2033 mysqld crashes when I create a fulltext index on a UTF8 encoded cjk column
Submitted: 6 Dec 2003 21:51 Modified: 7 Dec 2003 5:21
Reporter: Yiguang Hu
Status: Closed
Category:Server Severity:S1 (Critical)
Version:4.1.1apha OS:Linux (Linux 6.2)
Assigned to: Sergei Golubchik Target Version:

[6 Dec 2003 21:51] Yiguang Hu 
Description:
I have a table with 31114 records. One of the column is cjk (Contain double bytes chinese
character) in text and UTF8. I tried to create a fulltext index on this cjk text column
use the alter table command and it always crash the mysqld. 
The character_set_system and character_set_database are both UTF8.
The ft_min_word_len is 1.
The Stack trace report is:
0x8086bd3  +134769619
0x82d03c8  +137167816
0x82957c3  +136927171
0x7e28003f +2116550719

The cjk data is not corrupted in the table and I can query and save the data in a file and
data are all fine.

How to repeat:
I tried the following:
1. I tried to clean up my table and fill the cjk text column with ascii data and then the
alter command can create   the fulltext index and I can do full text search without any
problem. But if I drop the table and recreate the table and fill up the cjk data and then
alter table to create fulltext index would crash the mysqld immediately.
2. if the table has only one record, I can create the fulltext index on the cjk column
without problem.
[6 Dec 2003 21:53] Yiguang Hu 
stack trace report

Attachment: stacketrace.report (application/octet-stream, text), 94 bytes.
[6 Dec 2003 21:53] Yiguang Hu 
some variables

Attachment: variables (application/octet-stream, text), 226 bytes.
[7 Dec 2003 5:21] Sergei Golubchik 
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

fixed in 4.1.2
[7 Dec 2003 5:21] Sergei Golubchik 
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

fixed in 4.1.2