Bug #41745 Crash in Event_scheduler::dump_internal_status()
Submitted: 25 Dec 2008 13:59 Modified: 15 May 2010 8:52
Reporter: Philip Stoev Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:6.0.9 OS:Any
Assigned to: Philip Stoev CPU Architecture:Any

[25 Dec 2008 13:59] Philip Stoev
Description:
When executing rpl_sys under Falcon , the server crashed on startup as follows:

#3  <signal handler called>
#4  Event_scheduler::dump_internal_status (this=0x0) at event_scheduler.cc:792
#5  0x00000000007c95b3 in Events::dump_internal_status () at events.cc:1013
#6  0x00000000006dcc2e in mysql_print_status () at sql_test.cc:593
#7  0x000000000063b157 in signal_hand (arg=<value optimized out>) at mysqld.cc:2912
#8  0x000000315b0073da in start_thread () from /lib64/libpthread.so.0
#9  0x000000315a4e627d in clone () from /lib64/libc.so.6

How to repeat:
If this is repeatable, a simplifed test case will be provided.
[15 May 2010 8:52] Philip Stoev
One-time occurrence, not repeatable.