MySQL Bugs: #41626: crash in falcon_bug_34351

Bug #41626	crash in falcon_bug_34351_C in pushbuild
Submitted:	19 Dec 2008 7:37	Modified:	25 Mar 2009 14:34
Reporter:	Sven Sandberg	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server: Falcon storage engine	Severity:	S1 (Critical)
Version:	6.0	OS:	Any
Assigned to:	Assigned Account	CPU Architecture:	Any
Tags:	core, crash, F_PAGE IO, pushbuild, sporadic, test failure

Description:
Pushbuild failure, happened once. The stack traces from all threads are longer than the allowed limit for bug reports. I will attach the full output as a file.

falcon.falcon_bug_34351_C                [ fail ]
        Test ended at 2008-12-16 01:03:49

CURRENT_TEST: falcon.falcon_bug_34351_C

Could not execute 'check-warnings' for testcase 'falcon.falcon_bug_34351_C' (res: 1):
mysqltest: Could not open connection 'default': 2013 Lost connection to MySQL server at 'reading initial communication packet', system error: 104

 - saving '/dev/shm/var-falcon-112/log/falcon.falcon_bug_34351_C/' to '/dev/shm/var-falcon-112/log/falcon.falcon_bug_34351_C/'
 - found 'core.8608' (0/5)

Trying 'gdb' to get a backtrace
Core generated by '/data0/pushbuild/pb/bzr_mysql-6.0-rpl/125/mysql-6.0.9-alpha-pb125/sql/mysqld'
Output from gdb follows. The first stack trace is from the failing thread.
The following stack traces are from all threads (so the failing one is
duplicated).
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/data0/pushbuild/pb/bzr_mysql-6.0-rpl/125/mysql-6.0.9-alpha-pb125/sql/mysqld --'.
Program terminated with signal 6, Aborted.
#0  0x00002ab0e2ef14c5 in pthread_kill () from /lib64/libpthread.so.0
#0  0x00002ab0e2ef14c5 in pthread_kill () from /lib64/libpthread.so.0
#1  0x0000000000687e2e in handle_segfault (sig=6) at mysqld.cc:2667
#2  <signal handler called>
#3  0x00002ab0e2ef3fed in raise () from /lib64/libpthread.so.0
#4  0x00000000008f45e2 in Error::error (string=<value optimized out>)
    at Error.cpp:94
#5  0x00000000008d3e15 in Cache::fetchPage (this=0x2aaaaabd8ff0, 
    dbb=0x2aaaaadbc0d0, pageNumber=0, pageType=PAGE_data, lockType=Exclusive)
    at Cache.cpp:316
#6  0x000000000097a9c0 in RecordLocatorPage::deleteDataPages (
    this=0x2aaaaaff5000, dbb=0x2aaaaadbc0d0, transId=0)
    at RecordLocatorPage.cpp:434
#7  0x000000000092dc53 in Section::deleteSectionLevel (dbb=0x2aaaaadbc0d0, 
    pageNumber=14, transId=0) at Section.cpp:978
#8  0x000000000093c60f in SerialLogTransaction::commit (this=0x2aaaaefe3578)
    at SerialLogTransaction.cpp:92
#9  0x000000000096bcd4 in Gopher::gopherThread (this=0x2aaaaadb2b70)
    at Gopher.cpp:71
#10 0x00000000008c0bf4 in Thread::thread (this=0x2aaaaadc3ff0)
    at Thread.cpp:167
#11 0x00000000008c0dd9 in Thread::thread (parameter=0x21a0) at Thread.cpp:146
#12 0x00002ab0e2eed193 in start_thread () from /lib64/libpthread.so.0
#13 0x00002ab0e352047d in clone () from /lib64/libc.so.6
#14 0x0000000000000000 in ?? ()

[...]

How to repeat:
https://intranet.mysql.com/secure/pushbuild/showpush.pl?dir=bzr_mysql-6.0-rpl&order=125 sapsrv2/falcon
xref: http://tinyurl.com/3s5r5r

Sven, the attached file is a summary of 6 different pushbuild failures.  None of them refer to test 34351 or Cache::fetchPage which is on this call stack.  Ar you sure you attached the correct file?

Full output, including stack traces from all threads (ignore previous file)

Attachment: tmp.3 (application/octet-stream, text), 11.25 KiB.

Kevin, you are right, I attached the wrong file. I hid the wrong file and uploaded the right one.

This is another 'wrong page type' error.

This bug is a duplicate of Bug#39890 Falcon Error: page 0/1 wrong page type, expected 7 got 1