Comment 4 for bug 1384591

5.6 with TokuDB fails with:

Version: '5.6.31-76.4-debug-log' socket: '/home/sveta/build/ps-5.6/mysql-test/var/tmp/mysqld.1.sock' port: 13001 Source distribution
mysqld: /home/sveta/src/percona-server/sql/ha_partition.cc:5963: int ha_partition::handle_ordered_index_scan(uchar*, bool): Assertion `bitmap_is_set(&m_part_info->read_partitions, m_part_spec.start_part)' failed.
18:25:27 UTC - mysqld got signal 6 ;
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=1048576
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 = 61927 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7efd7b75b000
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 = 7efd87c33dc8 thread_stack 0x40000
/home/sveta/build/ps-5.6/bin/mysqld(my_print_stacktrace+0x38)[0xae6e13]
/home/sveta/build/ps-5.6/bin/mysqld(handle_fatal_signal+0x42d)[0x73e3ab]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10330)[0x7efd86bd4330]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7efd86006c37]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7efd8600a028]
/lib/x86_64-linux-gnu/libc.so.6(+0x2fbf6)[0x7efd85fffbf6]
/lib/x86_64-linux-gnu/libc.so.6(+0x2fca2)[0x7efd85fffca2]
/home/sveta/build/ps-5.6/bin/mysqld(_ZN12ha_partition25handle_ordered_index_scanEPhb+0x101)[0xe7db81]
/home/sveta/build/ps-5.6/bin/mysqld(_ZN12ha_partition17common_first_lastEPh+0x89)[0xe7ca3b]
/home/sveta/build/ps-5.6/bin/mysqld(_ZN12ha_partition10index_lastEPh+0x61)[0xe7c9af]
/home/sveta/build/ps-5.6/bin/mysqld(_ZN7handler13ha_index_lastEPh+0xf6)[0x64dcdc]
/home/sveta/build/ps-5.6/bin/mysqld[0x9a9c4a]
/home/sveta/build/ps-5.6/bin/mysqld(_Z13opt_sum_queryP3THDP10TABLE_LISTR4ListI4ItemEPS4_+0x87d)[0x9aa4c9]
/home/sveta/build/ps-5.6/bin/mysqld(_ZN4JOIN8optimizeEv+0xb79)[0x9e2a5d]
/home/sveta/build/ps-5.6/bin/mysqld[0x82aaed]
/home/sveta/build/ps-5.6/bin/mysqld(_Z12mysql_selectP3THDP10TABLE_LISTjR4ListI4ItemEPS4_P10SQL_I_ListI8st_orderESB_S7_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x220)[0x82adfc]
/home/sveta/build/ps-5.6/bin/mysqld(_Z13handle_selectP3THDP13select_resultm+0x1a6)[0x828d6c]
/home/sveta/build/ps-5.6/bin/mysqld[0x7ff69f]
/home/sveta/build/ps-5.6/bin/mysqld(_Z21mysql_execute_commandP3THD+0xe29)[0x7f76ff]
/home/sveta/build/ps-5.6/bin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x5a8)[0x80249c]
/home/sveta/build/ps-5.6/bin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0xd13)[0x7f3c43]
/home/sveta/build/ps-5.6/bin/mysqld(_Z10do_commandP3THD+0x3bb)[0x7f2af0]
/home/sveta/build/ps-5.6/bin/mysqld(_Z24do_handle_one_connectionP3THD+0x273)[0x7b9799]
/home/sveta/build/ps-5.6/bin/mysqld(handle_one_connection+0x33)[0x7b9231]
/home/sveta/build/ps-5.6/bin/mysqld(pfs_spawn_thread+0x147)[0xe5b462]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8184)[0x7efd86bcc184]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7efd860ca37d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7efd72c21010): SELECT MAX(a)FROM t1 WHERE a>5
Connection ID (thread ID): 4
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.
Writing a core file