Bug #26991 crash during SELECT in sql-bench/test-insert
Submitted: 9 Mar 2007 9:19 Modified: 21 Mar 2007 17:20
Reporter: Matthias Leich Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server: Falcon storage engine Severity:S1 (Critical)
Version:5.2 OS:
Assigned to: Matthias Leich CPU Architecture:Any

[9 Mar 2007 9:19] Matthias Leich
Description:
1. Run(one attempt) of the non modified test-insert with
   VARDIR on a RAM based filesystem -> sucess
2. Run(one attempt) of the non modified test-insert with
   VARDIR on a disk based filesystem
   -> failure (unexpected server error message around UPDATE)
3. Run(one attempt) of a modified (disable aborts on error)
   test-insert with VARDIR on a disk based filesystem
   -> Crash

thd: 0x17a4d70
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...
Cannot determine thread, fp=0x43885480, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x63f5b7 handle_segfault + 567
0x7d84f4 _ZN11Transaction12removeRecordEP13RecordVersion + 36
0x7d4aef _ZN5Table12unlockRecordEi + 95
0x7c2cc2 _ZN15NfsStorageTable10index_nextEPc + 146
0x7c0d1f _ZN15NfsStorageTable15index_next_sameEPcPKcj + 63
0x7121a6 _ZN7handler21read_multi_range_nextEPP18st_key_multi_range + 38
0x6f9fa0 _ZN18QUICK_RANGE_SELECT8get_nextEv + 336
0x70ec1d _Z8rr_quickP14st_read_record + 29
0x6a1ca8 _Z10sub_selectP4JOINP13st_join_tableb + 104
0x6a20cf _Z9do_selectP4JOINP4ListI4ItemEP8st_tableP9Procedure + 639
0x6b0b1c _ZN4JOIN4execEv + 1356
0x6b2a48 _Z12mysql_selectP3THDPPP4ItemP13st_table_listjR4ListIS1_ES2_jP8st_orderSB_S2_SB_mP13select_resultP18st_select_lex_unitP13st_sel + 344
0x6b3365 _Z13handle_selectP3THDP6st_lexP13select_resultm + 325
0x657971 _Z21execute_sqlcom_selectP3THDP13st_table_list + 161
0x65bfb5 _Z21mysql_execute_commandP3THD + 4645
0x661e75 _Z11mysql_parseP3THDPcj + 885
0x66232f _Z16dispatch_command19enum_server_commandP3THDPcj + 1119
0x66411a handle_one_connection + 2554
0x2b5f1c78709e _end + 460985166
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x17fb170 = SELECT bench1.* FROM bench1 WHERE id IN (1,2,3,4,5,6,7,8,9,10)
thd->thread_id=2

My environment:
- MySQL-5.1-falcon last ChangeSet@1.2467, 2007-03-06
  (compile-pentium-max)
- Linux openSUSE 10.2 (X86-64), Core2Duo (x86 64 Bit)

How to repeat:
Not yet available.
[21 Mar 2007 17:20] Matthias Leich
I made several attempts to reproduce the crash with
mysql-5.1-falcon last ChangeSet@1.2498.1.1, 2007-03-19
but only the unexpected server error message around UPDATE occured.
[21 Mar 2007 18:01] Matthias Leich
The unexpected server responses "Record has changed ..." are tracked in
Bug#27350 test-insert, Unexpected error; "Record has changed since last
          read in table"