Bug #3971 Fatal Crash of mysql Server when using parameters in select

• Submitted: 2 Jun 2004 17:51
• Modified: 20 Jun 2004 6:02
• Reporter: k self
• Status: Closed
• Category: MySQL Server
• Severity: S1 (Critical)
• Version: 5.0.0-alpha
• OS: Windows (Windows XP/Windows 2000)
• CPU Architecture: Any

[2 Jun 2004 17:51] k self

Description:
The MySQL Server will crash if parameters are used in the select statement of a command contained within the stored procedure.

selecting other values (constants, table columns etc.) do not cause the server to crash, and work as expected.

This bug was rated severity = critical because any bug that can crash a server via the command sql client line is a critical error.

How to repeat:
mysql> delimiter go
mysql>
mysql> create procedure myfatal_error(a int,b int)
    -> begin
    -> select a,b;
    -> end
    -> go
Query OK, 0 rows affected (0.01 sec)

mysql> call myfatal_error(1,1)
mysql> go

At this point, the client hangs, and the Server crashes.

Suggested fix:
None

[2 Jun 2004 20:53] MySQL Verification Team

Thank you for the bug report I was able to repeat with version 5.0.
I will verify it with our latest BK source.

[20 Jun 2004 6:02] MySQL Verification Team

I tested against latest BK 5.0 source tree and this issue was
already fixed:

mysql>  create procedure myfatal_error(a int,b int)
    ->  begin
    -> select a,b;
    ->  end
    -> go
Query OK, 0 rows affected (0.00 sec)

mysql>

mysql> call myfatal_error(1,1)
    -> go
+---+---+
| a | b |
+---+---+
| 1 | 1 |
+---+---+
1 row in set (0.00 sec