2014-10-08 06:02:03 31808 [Note] Plugin 'FEDERATED' is disabled.
2014-10-08 06:02:03 31808 [Note] InnoDB: Using atomics to ref count buffer pool pages
2014-10-08 06:02:03 7fe75248d740 InnoDB: !!!!!!!! UNIV_DEBUG switched on !!!!!!!!!
2014-10-08 06:02:03 7fe75248d740 InnoDB: !!!!!!!! UNIV_SYNC_DEBUG switched on !!!!!!!!!
2014-10-08 06:02:03 31808 [Note] InnoDB: The InnoDB memory heap is disabled
2014-10-08 06:02:03 31808 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2014-10-08 06:02:03 31808 [Note] InnoDB: Memory barrier is not used
2014-10-08 06:02:03 31808 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-10-08 06:02:03 31808 [Note] InnoDB: Using Linux native AIO
2014-10-08 06:02:03 31808 [Note] InnoDB: Using CPU crc32 instructions
2014-10-08 06:02:03 31808 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-10-08 06:02:03 31808 [Note] InnoDB: Completed initialization of buffer pool
2014-10-08 06:02:03 31808 [Note] InnoDB: Highest supported file format is Barracuda.
2014-10-08 06:02:03 31808 [Note] InnoDB: The log sequence numbers 1626007 and 1626007 in ibdata files do not match the log sequence number 1626017 in the ib_logfiles!
2014-10-08 06:02:03 31808 [Note] InnoDB: Database was not shutdown normally!
2014-10-08 06:02:03 31808 [Note] InnoDB: Starting crash recovery.
2014-10-08 06:02:03 31808 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-10-08 06:02:03 31808 [Note] InnoDB: Restoring possible half-written data pages 
2014-10-08 06:02:03 31808 [Note] InnoDB: from the doublewrite buffer...
2014-10-08 06:02:05 31808 [Note] InnoDB: 128 rollback segment(s) are active.
2014-10-08 06:02:05 31808 [Note] InnoDB: Waiting for purge to start
2014-10-08 06:02:05 31808 [Note] InnoDB: 5.6.20 started; log sequence number 1626017
2014-10-08 06:02:05 31808 [Note] Server hostname (bind-address): '*'; port: 3307
2014-10-08 06:02:05 31808 [Note] IPv6 is available.
2014-10-08 06:02:05 31808 [Note]   - '::' resolves to '::';
2014-10-08 06:02:05 31808 [Note] Server socket created on IP: '::'.
2014-10-08 06:02:05 31808 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_account_by_event_name' has the wrong structure
2014-10-08 06:02:05 31808 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_user_by_event_name' has the wrong structure
2014-10-08 06:02:05 31808 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_host_by_event_name' has the wrong structure
2014-10-08 06:02:05 31808 [ERROR] Native table 'performance_schema'.'events_statements_summary_global_by_event_name' has the wrong structure
2014-10-08 06:02:05 31808 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_digest' has the wrong structure
2014-10-08 06:02:05 31808 [ERROR] Native table 'performance_schema'.'users' has the wrong structure
2014-10-08 06:02:05 31808 [ERROR] Native table 'performance_schema'.'accounts' has the wrong structure
2014-10-08 06:02:05 31808 [ERROR] Native table 'performance_schema'.'hosts' has the wrong structure
2014-10-08 06:02:05 31808 [ERROR] Native table 'performance_schema'.'session_connect_attrs' has the wrong structure
2014-10-08 06:02:05 31808 [ERROR] Native table 'performance_schema'.'session_account_connect_attrs' has the wrong structure
2014-10-08 06:02:05 31808 [Note] Event Scheduler: Loaded 0 events
2014-10-08 06:02:05 31808 [Note] /ssd/ramesh/mysql-server/mysql-5.6.20-linux-x86_64-debug/bin/mysqld: ready for connections.
Version: '5.6.20-debug'  socket: '/ssd/ramesh/testdb/mysql.sock'  port: 3307  MySQL Community Server (GPL)
mysqld: /ssd/ramesh/mysql-server/mysql-5.6/sql/filesort.cc:1026: void make_sortkey(Sort_param*, uchar*, uchar*): Assertion `sort_field->length >= length' failed.
06:02:41 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.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=1
max_threads=151
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 = 68249 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x1ee1530
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 = 7fe720679e60 thread_stack 0x40000
/ssd/ramesh/mysql-server/mysql-5.6.20-linux-x86_64-debug/bin/mysqld(my_print_stacktrace+0x35)[0xa902dc]
/ssd/ramesh/mysql-server/mysql-5.6.20-linux-x86_64-debug/bin/mysqld(handle_fatal_signal+0x3f3)[0x7234a3]
/lib64/libpthread.so.0(+0xf130)[0x7fe752073130]
/lib64/libc.so.6(gsignal+0x39)[0x7fe750e7c5c9]
/lib64/libc.so.6(abort+0x148)[0x7fe750e7dcd8]
/lib64/libc.so.6(+0x2e536)[0x7fe750e75536]
/lib64/libc.so.6(+0x2e5e2)[0x7fe750e755e2]
/ssd/ramesh/mysql-server/mysql-5.6.20-linux-x86_64-debug/bin/mysqld(_Z12make_sortkeyP10Sort_paramPhS1_+0x2ca)[0x917d07]
/ssd/ramesh/mysql-server/mysql-5.6.20-linux-x86_64-debug/bin/mysqld[0x91735c]
/ssd/ramesh/mysql-server/mysql-5.6.20-linux-x86_64-debug/bin/mysqld(_Z8filesortP3THDP5TABLEP8FilesortbPyS5_+0x8ca)[0x915b31]
/ssd/ramesh/mysql-server/mysql-5.6.20-linux-x86_64-debug/bin/mysqld[0x7a570f]
/ssd/ramesh/mysql-server/mysql-5.6.20-linux-x86_64-debug/bin/mysqld(_ZN13st_join_table10sort_tableEv+0x121)[0x7a3245]
/ssd/ramesh/mysql-server/mysql-5.6.20-linux-x86_64-debug/bin/mysqld(_Z21join_init_read_recordP13st_join_table+0x61)[0x7a2d14]
/ssd/ramesh/mysql-server/mysql-5.6.20-linux-x86_64-debug/bin/mysqld(_Z10sub_selectP4JOINP13st_join_tableb+0x1b5)[0x7a061b]
/ssd/ramesh/mysql-server/mysql-5.6.20-linux-x86_64-debug/bin/mysqld[0x7a0005]
/ssd/ramesh/mysql-server/mysql-5.6.20-linux-x86_64-debug/bin/mysqld(_ZN4JOIN4execEv+0x6a5)[0x79df61]
/ssd/ramesh/mysql-server/mysql-5.6.20-linux-x86_64-debug/bin/mysqld[0x7fe143]
/ssd/ramesh/mysql-server/mysql-5.6.20-linux-x86_64-debug/bin/mysqld(_Z12mysql_selectP3THDP10TABLE_LISTjR4ListI4ItemEPS4_P10SQL_I_ListI8st_orderESB_S7_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x24c)[0x7fe43f]
/ssd/ramesh/mysql-server/mysql-5.6.20-linux-x86_64-debug/bin/mysqld(_Z13handle_selectP3THDP13select_resultm+0x1d5)[0x7fc4c7]
/ssd/ramesh/mysql-server/mysql-5.6.20-linux-x86_64-debug/bin/mysqld[0x7d681b]
/ssd/ramesh/mysql-server/mysql-5.6.20-linux-x86_64-debug/bin/mysqld(_Z21mysql_execute_commandP3THD+0xca3)[0x7cf5cb]
/ssd/ramesh/mysql-server/mysql-5.6.20-linux-x86_64-debug/bin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x485)[0x7d8fa4]
/ssd/ramesh/mysql-server/mysql-5.6.20-linux-x86_64-debug/bin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0xcbe)[0x7cc557]
/ssd/ramesh/mysql-server/mysql-5.6.20-linux-x86_64-debug/bin/mysqld(_Z10do_commandP3THD+0x33e)[0x7cb646]
/ssd/ramesh/mysql-server/mysql-5.6.20-linux-x86_64-debug/bin/mysqld(_Z24do_handle_one_connectionP3THD+0x1b6)[0x793a61]
/ssd/ramesh/mysql-server/mysql-5.6.20-linux-x86_64-debug/bin/mysqld(handle_one_connection+0x33)[0x79354a]
/ssd/ramesh/mysql-server/mysql-5.6.20-linux-x86_64-debug/bin/mysqld(pfs_spawn_thread+0x159)[0xad4b5c]
/lib64/libpthread.so.0(+0x7df3)[0x7fe75206bdf3]
/lib64/libc.so.6(clone+0x6d)[0x7fe750f3d01d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fe6ec004fd0): SELECT 1 FROM t1 ORDER BY @x:=makedate(a,a)
Connection ID (thread ID): 1
Status: NOT_KILLED

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.