Bug #54227 crash when select archive table

Description:
I have build a table offer_his using table engine archive.
But when I select from from the table. mysqld crashed.

How to repeat:
1、将offer_his.ARZ和 offer_his.frm拷贝到数据库目录下 
2、修改offer_his.ARZ和offer_his.frm的为mysql:mysql chown mysql:mysql offer_his.*。如果有必要，修改属性 chmod 660 offer_his.*
3、登录mysql.输入 show create table offer_his;

mysql将会重启。日志文件里面输出为 ：
100519 10:31:37 [Note] Event Scheduler: scheduler thread started with id 3
100519 10:31:44 [ERROR] /usr/sbin/mysqld: Table './monitor/xdual' is marked as crashed and should be repaired
100519 10:31:44 [Warning] Checking table:   './monitor/xdual'
100519 11:04:37 - 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=33554432
read_buffer_size=2097152
max_used_connections=69
max_threads=3000
threads_connected=69
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 12351307 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x2aaef40146b0
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...
stack_bottom = 0x471d9f20 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x8455ee]
100519 11:04:37 mysqld_safe Number of processes running now: 0
100519 11:04:37 mysqld_safe mysqld restarted
InnoDB: Log scan progressed past the checkpoint lsn 203 1667917151
100519 11:04:40  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.

Suggested fix:
no

i can not upload offer_his.ARZ because of "Maximum allowed size is 500KB.". it is about 24M.

Thank you for the bug report. Could you please try latest released version 5.1.47. Thanks in advance.

it does not crash in mysql 5.1.47.

Not repeatable with recent 5.1.x versions.