MySQL Bugs: #37684: Big bug in Mysql 64bit

Bug #37684	Big bug in Mysql 64bit - Crash!!!
Submitted:	27 Jun 2008 7:35	Modified:	27 Jul 2008 12:48
Reporter:	www www	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: MyISAM storage engine	Severity:	S2 (Serious)
Version:	5.0.51a	OS:	Linux (opensuse 10.3 64bit)
Assigned to:		CPU Architecture:	Any
Tags:	64bit, crash

Description:
Please user the attachment(t_tribe_photo_map.sql) to create a table named t_tribe_photo_map,and use the SQL below:

select photo_id from t_tribe_photo_map where tribe_id = 1900414 and category_id = 103 and photo_id < 76 order by photo_id desc limit 1;

The Mysql Server is Crash and you will get the message:

mysql> select photo_id from t_tribe_photo_map where tribe_id = 1900426 and category_id = 114 and photo_id < 121 order by photo_id desc limit 1;
ERROR 2013 (HY000): Lost connection to MySQL server during query

How to repeat:
Please user the attachment(t_tribe_photo_map.sql) to create a table named t_tribe_photo_map,and use the SQL below:

select photo_id from t_tribe_photo_map where tribe_id = 1900414 and category_id = 103 and photo_id < 76 order by photo_id desc limit 1;

The Mysql Server is Crash and you will get the message:

mysql> select photo_id from t_tribe_photo_map where tribe_id = 1900426 and category_id = 114 and photo_id < 121 order by photo_id desc limit 1;
ERROR 2013 (HY000): Lost connection to MySQL server during query

the table struct and data.

Attachment: t_tribe_photo_map.sql (text/plain), 58.18 KiB.

Please use not user.

type the wrong word,sorry.

Many thanks for writing a bug report.

Unfortunately I can't reproduce this by using MySQL 5.0.51b.

All works fine here.

How did you install MySQL?

MySQL 5.0.51a also is a little bit old. Please try with MySQL 5.0.51b and let us now, if you will get this problem there too.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".