MySQL Bugs: #7730: Server crash using soundex on an utf8 table

Bug #7730	Server crash using soundex on an utf8 table
Submitted:	7 Jan 2005 13:44	Modified:	12 Jan 2005 7:21
Reporter:	Support AdequateSystems	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server	Severity:	S3 (Non-critical)
Version:	4.1.8/4.1.9 BK/5.0.3 BK	OS:	Linux (MandrakeLinux 10.1 AMD 64)
Assigned to:	Alexander Barkov	CPU Architecture:	Any

Description:
Server crash.

Here is the error log :

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=67108864
read_buffer_size=1044480
max_used_connections=5
max_connections=100
threads_connected=5
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 269935 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Number of processes running now: 0
050107 14:38:47  mysqld restarted
050107 14:38:47  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...
050107 14:38:47  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 68112520.
InnoDB: Doing recovery: scanned up to log sequence number 0 68112520
InnoDB: Last MySQL binlog file position 0 65039, file name ./dhcppc0-bin.000016
050107 14:38:48  InnoDB: Flushing modified pages from the buffer pool...
050107 14:38:48  InnoDB: Started; log sequence number 0 68112520
/usr/sbin/mysqld: ready for connections.
Version: '4.1.8-standard-log'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  Official MySQL RPM

How to repeat:
create database test character set utf8 collate utf8_unicode_ci;
use test;

create table test (id integer, field varchar(100));
insert into test values (1, 'Test');

select * from test where soundex(field) = soundex('Test');
=> Crash here

Thank you for the bug report I was able to repeat with server
from BK source 4.1 tree.

Verified also on 5.0 BK source.

The bug also seems to occur with MyISAM tables. So, I removed "innodb" from synopsis.

Fixed in 4.1.9.
Waiting for merge into 5.0.3.

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 5.0.3