Bug #20156 Events: crash if variable for interval
Submitted: 30 May 2006 22:22 Modified: 31 May 2006 8:03
Reporter: Peter Gulutzan Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Stored Routines Severity:S3 (Non-critical)
Version:5.1.2-beta-debug OS:Linux (SUSE 10.0 / 64-bit)
Assigned to: CPU Architecture:Any

[30 May 2006 22:22] Peter Gulutzan 
Description:
I say CREATE EVENT ... INTERVAL declared_variable SECOND ... in a stored procedure.
Crash.

This is very similar to bug#16409 and perhaps the fix for bug#18896 will take care of it.

How to repeat:
mysql> create procedure pp () begin declare v int; create event e on schedule every v second do set v = v + 1; end//
ERROR 2013 (HY000): Lost connection to MySQL server during query
[30 May 2006 22:59] MySQL Verification Team 
Thank you for the bug report.

Version: '5.1.12-beta-debug'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
[New Thread 1116425136 (LWP 6778)]
060530 19:37:42 [Note] SCHEDULER: Manager thread booting
060530 19:37:42 [Note] SCHEDULER: Loaded 0 events
060530 19:37:42 [Note] SCHEDULER: Suspending operations
[New Thread 1116625840 (LWP 6780)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1116625840 (LWP 6780)]
0x081a37e2 in Item_splocal::this_item (this=0x92f5230) at item.cc:933
933       DBUG_ASSERT(m_sp == m_thd->spcont->sp);
[31 May 2006 8:03] Andrey Hristov 
Yes, this one is additional side effect of the reasons for 18896.