Replication crash: mysqld got signal 11

Server configuration:
 MASTER (5.0.32-Debian_7etch10-log)
 SLAVE (Percona 5.1.66-rel14.1-log)

After SLAVE setup we have such error:

19:08:47 UTC - 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.
Please help us make Percona Server better by reporting any
bugs at http://bugs.percona.com/

key_buffer_size=536870912
read_buffer_size=2097152
max_used_connections=6
max_threads=200
thread_count=2
connection_count=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1345713 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x422acc0
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 = 7f1e1038aea8 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x8c9fc5]
/usr/sbin/mysqld(handle_fatal_signal+0x40b)[0x6c339b]
/lib/libpthread.so.0(+0xeff0)[0x7f1e10033ff0]
/usr/sbin/mysqld(_Z36fill_record_n_invoke_before_triggersP3THDR4ListI4ItemES4_bP19Table_triggers_list14trg_event_type+0x48)[0x619428]
/usr/sbin/mysqld(_Z12mysql_updateP3THDP10TABLE_LISTR4ListI4ItemES6_PS4_jP8st_ordery15enum_duplicatesb+0xa75)[0x661585]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x9e0)[0x5e3b20]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjPPKc+0x4fb)[0x5e8bdb]
/usr/sbin/mysqld(_ZN15Query_log_event14do_apply_eventEPK14Relay_log_infoPKcj+0x40e)[0x6906ee]
/usr/sbin/mysqld(_Z26apply_event_and_update_posP9Log_eventP3THDP14Relay_log_info+0xfd)[0x6fa92d]
/usr/sbin/mysqld(handle_slave_sql+0x78f)[0x6fc78f]
/lib/libpthread.so.0(+0x68ca)[0x7f1e1002b8ca]
/lib/libc.so.6(clone+0x6d)[0x7f1e0ee95b6d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (44b4020):
Connection ID (thread ID): 473
Status: NOT_KILLED

You may download the Percona Server operations manual by visiting
http://www.percona.com/software/percona-server/. You may find information
in the manual which will help you identify the cause of the crash.
121121 21:08:47 mysqld_safe Number of processes running now: 0
121121 21:08:47 mysqld_safe mysqld restarted
121121 21:08:48 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3.4
121121 21:08:48 InnoDB: Initializing buffer pool, size = 512.0M
121121 21:08:48 InnoDB: Completed initialization of buffer pool
121121 21:08:48 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 27963600506
121121 21:08:48 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...
InnoDB: Doing recovery: scanned up to log sequence number 27965138225
121121 21:08:48 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: In a MySQL replication slave the last master binlog file
InnoDB: position 0 492571676, file name mysql-bin.002907
InnoDB: and relay log file
InnoDB: position 0 14181208, file name ./mysqld-relay-bin.000002
InnoDB: Last MySQL binlog file position 0 106, file name /var/log/mysql/mysql-bin.000010
121121 21:08:48 Percona XtraDB (http://www.percona.com) 1.0.17-14.1 started; log sequence number 27965138225
121121 21:08:48 [Note] Recovering after a crash using /var/log/mysql/mysql-bin
121121 21:08:48 [Note] Starting crash recovery...
121121 21:08:48 [Note] Crash recovery finished.
121121 21:08:48 [Note] Event Scheduler: Loaded 0 events
121121 21:08:48 [Note] /usr/sbin/mysqld: ready for connections.

=====================

MySQL backtrace:

Thread pointer: 0x263a720
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 = 7fed3f349ea8 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x8c9fc5]
/usr/sbin/mysqld(handle_fatal_signal+0x40b)[0x6c339b]
/lib/libpthread.so.0(+0xeff0)[0x7fed3eff2ff0]
/lib/libc.so.6(+0x1071b6)[0x7fed3de8c1b6]
/usr/sbin/mysqld(my_charset_same+0x1b)[0x8c4c9b]
/usr/sbin/mysqld(_ZN6String16needs_conversionEjP15charset_info_stS1_Pj+0x58)[0x5cfe48]
/usr/sbin/mysqld(_ZN10Field_enum5storeEPKcjP15charset_info_st+0x5d)[0x5b92ad]
/usr/sbin/mysqld(_ZN4Item13save_in_fieldEP5Fieldb+0xd8)[0x531718]
/usr/sbin/mysqld(_Z36fill_record_n_invoke_before_triggersP3THDR4ListI4ItemES4_bP19Table_triggers_list14trg_event_type+0x90)[0x619470]
/usr/sbin/mysqld(_Z12mysql_updateP3THDP10TABLE_LISTR4ListI4ItemES6_PS4_jP8st_ordery15enum_duplicatesb+0xa75)[0x661585]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x9e0)[0x5e3b20]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjPPKc+0x4fb)[0x5e8bdb]
/usr/sbin/mysqld(_ZN15Query_log_event14do_apply_eventEPK14Relay_log_infoPKcj+0x40e)[0x6906ee]
/usr/sbin/mysqld(_Z26apply_event_and_update_posP9Log_eventP3THDP14Relay_log_info+0xfd)[0x6fa92d]
/usr/sbin/mysqld(handle_slave_sql+0x78f)[0x6fc78f]
/lib/libpthread.so.0(+0x68ca)[0x7fed3efea8ca]
/lib/libc.so.6(clone+0x6d)[0x7fed3de54b6d]

==============

Relay log after crash:

# at 4
#121121 21:07:48 server id 6 end_log_pos 106 Start: binlog v 4, server v 5.1.66-rel14.1-log created 121121 21:07:48
BINLOG '
hCatUA8GAAAAZgAAAGoAAAAAAAQANS4xLjY2LXJlbDE0LjEtbG9nAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAEzgNAAgAEgAEBAQEEgAAUwAEGggAAAAICAgC
'/*!*/;
# at 149
#121121 7:47:54 server id 1 end_log_pos 0 Start: binlog v 4, server v 5.0.32-Debian_7etch10-log created 121121 7:47:54
BINLOG '
CmusUA8BAAAAXgAAAAAAAAAAAAQANS4wLjMyLURlYmlhbl83ZXRjaDEwLWxvZwAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAEzgNAAgAEgAEBAQEEgAASwAEGg==
'/*!*/;
# at 14269994
#121121 18:30:40 server id 1 end_log_pos 492660502 User_var
SET @`0`:=_utf8 0x6F6E6C696E65 COLLATE `utf8_general_ci`/*!*/;
# at 14270034
#121121 18:30:40 server id 1 end_log_pos 492660537 User_var
SET @`1`:=_utf8 0x31 COLLATE `utf8_general_ci`/*!*/;

==================

And also tables are marked as crached:

121121 22:33:08 [ERROR] /usr/sbin/mysqld: Table './system/cron_job_run' is marked as crashed and should be repaired
121121 22:33:08 [Warning] Checking table: './system/cron_job_run'

==================

More info:

Before this, MASTER was the same (5.0.32-Debian_7etch10-log), SLAVE was (5.0.51a-24-log). Everything worked fine.

I suggest handling this problem as a bug (which it most likely is), rather than a question.