直接上日志:
thd: 0x1c1a50f0
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...
InnoDB: Thread 9912 stopped in file G:\mysql-6.0.11-alpha-winbuild\mysql-community-nt-6.0.11-alpha-build\storage\innobase\include\sync0sync.ic line 115
InnoDB: Thread 4064 stopped in file G:\mysql-6.0.11-alpha-winbuild\mysql-community-nt-6.0.11-alpha-build\storage\innobase\include\sync0sync.ic line 115
0000000140364105 mysqld.exe!btr_pcur_restore_position()[btr0pcur.c:217]
0000000140305687 mysqld.exe!row_unlock_for_mysql()[row0mysql.c:1546]
00000001402F73C5 mysqld.exe!ha_innobase::unlock_row()[ha_innodb.cc:4243]
000000014015A800 mysqld.exe!evaluate_join_record()[sql_select.cc:16569]
000000014015CBBE mysqld.exe!sub_select()[sql_select.cc:16303]
000000014015DBFC