Comment 31 for bug 1417810

Looks like the crash is 32bit + percona. Vanilla mysqld is ok on both 32 & 64 bit installs. Linux kernel doesn't matter. Here's the complete set of tests I did:

# Note: max_allowed_packet must be > 20M

3.14.29-grsec + 5.5.32-percona src (32bit): crash
3.2.59-grsec + 5.5.40-percona src (32bit): crash
3.2.59-grsec + 5.5.41-percona src (32bit): crash
3.14.29-grsec + 5.5.40-percona src (32bit): crash
3.14.29-grsec + 5.5.41-percona src (32bit): crash

3.14.29-grsec + 5.5.41-percona src + innodb_log_file_size = 256M + innodb_log_buffer_size = 1G (32bit): crash

3.16.0-30-generic #40-Ubuntu + percona 5.5.41-rel37.0-727.wheezy (32bit): crash
3.16.0-30-generic #40-Ubuntu + 5.5.41-rel37.0-727.wheezy (64bit): OK

3.16.0-30-generic #40-Ubuntu + 5.5.40-0+wheezy1 + mysql 5.5.40-0+wheezy1 (32bit): OK

As to which statement size crashes it:

 UPDATE wp_options SET option_value=REPEAT('x', $SIZE) WHERE option_id=1;

On two different servers, there's slight difference:
 - 3.14.29-grsec + 5.5.41-percona src (32bit):
$SIZE=16722688 is OK
$SIZE=167226989 crashes the server

 - 3.16.0-30-generic #40-Ubuntu + percona 5.5.41-rel37.0-727.wheezy (32bit):
$SIZE=16722689 is OK
$SIZE=16722690 crashes the server