Comment 48 for bug 1371827

Got another assertion when we redirect below testcase three times in to the server

DROP DATABASE test;CREATE DATABASE test;USE test;
create TABLE t0(i int,j int)ENGINE=innodb;
FLUSH TABLES t0 FOR EXPORT;
LOCK BINLOG FOR BACKUP;

** Testcase redirection command

/ssd/ramesh/Percona-Server-5.6.21-rel70.0-693.Linux.x86_64/bin/mysql -A -uroot -S/ssd/ramesh/Percona-Server-5.6.21-rel70.0-693.Linux.x86_64/socket.sock test < testcase.sql

*** GDB info

************ GDB
+bt
#0 0x00007f4ea139a771 in pthread_kill () from /lib64/libpthread.so.0
#1 0x000000000067679d in handle_fatal_signal (sig=11) at /mnt/workspace/percona-server-5.6-binaries-opt-yassl/label_exp/centos6-64/percona-server-5.6.21-70.0/sql/signal_handler.cc:236
#2 <signal handler called>
#3 operator() (this=<synthetic pointer>, thr=...) at /mnt/workspace/percona-server-5.6-binaries-opt-yassl/label_exp/centos6-64/percona-server-5.6.21-70.0/extra/yassl/src/yassl_int.cpp:1722
#4 find_if<mySTL::list<yaSSL::ThreadError>::iterator, yaSSL::yassl_int_cpp_local2::thr_match> (pred=..., last=..., first=...) at /mnt/workspace/percona-server-5.6-binaries-opt-yassl/label_exp/centos6-64/percona-server-5.6.21-70.0/extra/yassl/taocrypt/mySTL/algorithm.hpp:68
#5 yaSSL::Errors::Remove (this=0x7f4de9022040) at /mnt/workspace/percona-server-5.6-binaries-opt-yassl/label_exp/centos6-64/percona-server-5.6.21-70.0/extra/yassl/src/yassl_int.cpp:1791
#6 0x00000000005ad824 in one_thread_per_connection_end (thd=0x7f4e04f84000, block_pthread=true) at /mnt/workspace/percona-server-5.6-binaries-opt-yassl/label_exp/centos6-64/percona-server-5.6.21-70.0/sql/mysqld.cc:2843
#7 0x00000000006cb346 in do_handle_one_connection (thd_arg=thd_arg@entry=0x7f4e10f23000) at /mnt/workspace/percona-server-5.6-binaries-opt-yassl/label_exp/centos6-64/percona-server-5.6.21-70.0/sql/sql_connect.cc:1546
#8 0x00000000006cb4b0 in handle_one_connection (arg=arg@entry=0x7f4e10f23000) at /mnt/workspace/percona-server-5.6-binaries-opt-yassl/label_exp/centos6-64/percona-server-5.6.21-70.0/sql/sql_connect.cc:1443
#9 0x0000000000af86d3 in pfs_spawn_thread (arg=0x7f4e10f393e0) at /mnt/workspace/percona-server-5.6-binaries-opt-yassl/label_exp/centos6-64/percona-server-5.6.21-70.0/storage/perfschema/pfs.cc:1860
#10 0x00007f4ea1395df3 in start_thread () from /lib64/libpthread.so.0
#11 0x00007f4ea005f01d in clone () from /lib64/libc.so.6

************* Error

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=1
max_threads=153
thread_count=1
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 69184 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f03a9f92000
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 = 7f0446c30e40 thread_stack 0x40000
/ssd/ramesh/Percona-Server-5.6.21-rel70.0-693.Linux.x86_64/bin/mysqld(my_print_stacktrace+0x2c)[0x8e9f2c]
/ssd/ramesh/Percona-Server-5.6.21-rel70.0-693.Linux.x86_64/bin/mysqld(handle_fatal_signal+0x461)[0x676831]
/lib64/libpthread.so.0(+0xf130)[0x7f0446683130]
/ssd/ramesh/Percona-Server-5.6.21-rel70.0-693.Linux.x86_64/bin/mysqld[0xbb7de0]
/ssd/ramesh/Percona-Server-5.6.21-rel70.0-693.Linux.x86_64/bin/mysqld(_Z29one_thread_per_connection_endP3THDb+0x44)[0x5ad824]
/ssd/ramesh/Percona-Server-5.6.21-rel70.0-693.Linux.x86_64/bin/mysqld(_Z24do_handle_one_connectionP3THD+0xe6)[0x6cb346]
/ssd/ramesh/Percona-Server-5.6.21-rel70.0-693.Linux.x86_64/bin/mysqld(handle_one_connection+0x40)[0x6cb4b0]
/ssd/ramesh/Percona-Server-5.6.21-rel70.0-693.Linux.x86_64/bin/mysqld(pfs_spawn_thread+0x143)[0xaf86d3]
/lib64/libpthread.so.0(+0x7df3)[0x7f044667bdf3]
/lib64/libc.so.6(clone+0x6d)[0x7f044534501d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): Connection ID (thread ID): 3
Status: KILL_CONNECTION

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.
Writing a core file