Same with 5.6.39:

openxs@ao756:~/dbs/p5.5$ bash ~/ps_crash.sh
ERROR 2013 (HY000) at line 1: Lost connection to MySQL server during query
openxs@ao756:~/dbs/p5.5$ 140905 18:52:15 mysqld_safe Number of processes running now: 0
140905 18:52:15 mysqld_safe mysqld restarted

openxs@ao756:~/dbs/p5.5$ tail -100 data/ao756.err
140905 18:50:15 [ERROR] Aborting

140905 18:50:15  InnoDB: Starting shutdown...
140905 18:50:19  InnoDB: Shutdown completed; log sequence number 12744989
140905 18:50:19 [Note] /home/openxs/dbs/p5.5/bin/mysqld: Shutdown complete

140905 18:50:19 mysqld_safe mysqld from pid file /home/openxs/dbs/p5.5/data/ao756.pid ended
140905 18:50:45 mysqld_safe Starting mysqld daemon with databases from /home/openxs/dbs/p5.5/data
140905 18:50:45 [Note] Plugin 'FEDERATED' is disabled.
140905 18:50:45 InnoDB: The InnoDB memory heap is disabled
140905 18:50:45 InnoDB: Mutexes and rw_locks use GCC atomic builtins
140905 18:50:45 InnoDB: Compressed tables use zlib 1.2.3
140905 18:50:45 InnoDB: Using Linux native AIO
140905 18:50:45 InnoDB: Initializing buffer pool, size = 128.0M
140905 18:50:45 InnoDB: Completed initialization of buffer pool
140905 18:50:45 InnoDB: highest supported file format is Barracuda.
140905 18:50:45  InnoDB: Waiting for the background threads to start
140905 18:50:46 Percona XtraDB (http://www.percona.com) 5.5.39-36.0 started; log sequence number 12744989
140905 18:50:46 [Note] Event Scheduler: Loaded 0 events
140905 18:50:46 [Note] /home/openxs/dbs/p5.5/bin/mysqld: ready for connections.
Version: '5.5.39-36.0'  socket: '/tmp/mysql.sock'  port: 3306  MySQL Community Server (GPL)
15:52:15 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=8388608
read_buffer_size=131072
max_used_connections=1
max_threads=153
thread_count=1
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 343008 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x2585440
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 = 7f63b0256e70 thread_stack 0x40000
/home/openxs/dbs/p5.5/bin/mysqld(my_print_stacktrace+0x2c)[0x7c938c]
/home/openxs/dbs/p5.5/bin/mysqld(handle_fatal_signal+0x4a1)[0x6968c1]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7f63b41b3340]
/lib/x86_64-linux-gnu/libc.so.6(+0x140d5a)[0x7f63b3913d5a]
/home/openxs/dbs/p5.5/bin/mysqld[0x96bc6d]
/home/openxs/dbs/p5.5/bin/mysqld[0x8d2c41]
/home/openxs/dbs/p5.5/bin/mysqld[0x8d7ac5]
/home/openxs/dbs/p5.5/bin/mysqld[0x84cdb2]
/home/openxs/dbs/p5.5/bin/mysqld[0x825c91]
/home/openxs/dbs/p5.5/bin/mysqld(_Z18mysql_rename_tableP10handlertonPKcS2_S2_S2_j+0x13b)[0x603d6b]
/home/openxs/dbs/p5.5/bin/mysqld(_Z17mysql_alter_tableP3THDPcS1_P24st_ha_create_informationP10TABLE_LISTP10Alter_infojP8st_orderb+0x280a)[0x60870a]
/home/openxs/dbs/p5.5/bin/mysqld(_ZN21Alter_table_statement7executeEP3THD+0x4a5)[0x7a2a55]
/home/openxs/dbs/p5.5/bin/mysqld(_Z21mysql_execute_commandP3THD+0x3703)[0x59db33]
/home/openxs/dbs/p5.5/bin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x2d1)[0x5a1551]
/home/openxs/dbs/p5.5/bin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1ce3)[0x5a3b03]
/home/openxs/dbs/p5.5/bin/mysqld(_Z24do_handle_one_connectionP3THD+0x13a)[0x64120a]
/home/openxs/dbs/p5.5/bin/mysqld(handle_one_connection+0x4a)[0x6412fa]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8182)[0x7f63b41ab182]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f63b38cdfbd]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f6390004b60): ALTER TABLE testTable20 DROP FOREIGN KEY testTable20_ibfk_1
Connection ID (thread ID): 1
Status: NOT_KILLED
...