MySQL Bugs: #20274: mysqld crashed when using stored procedure

Bug #20274	mysqld crashed when using stored procedure
Submitted:	5 Jun 2006 21:04	Modified:	7 Jul 2006 13:54
Reporter:	[ name withheld ]	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S3 (Non-critical)
Version:	5.0.22	OS:	Linux (Linux)
Assigned to:		CPU Architecture:	Any

Description:
MySQL crashed when using a stored procedure.

Here is the stored procedure code.

DELIMITER //;
 
DROP PROCEDURE IF EXISTS `vj_node`.`DeleteEntry`//
 
CREATE DEFINER=`user`@`%` PROCEDURE `DeleteEntry`(
IN i_entry_id INT
,IN i_journal_id INT)
    DETERMINISTIC
BEGIN
DELETE me FROM media_entry AS me, media_member AS mm
WHERE i_journal_id = mm.parent_journal_id
AND i_entry_id = mm.parent_entry_id
AND mm.parent_journal_id = mm.media_journal_id
AND mm.media_journal_id = me.journal_id
AND mm.media_entry_id = me.entry_id;
DELETE FROM entry
WHERE i_journal_id = journal_id
AND i_entry_id = entry_id;
END//
 
DELIMITER ;//

The crash occured on the first DELETE statement

Here is the stack trace....

0x817ab50
0xeddf88
0x8
0x8193f18
0x827c6d1
0x827c469
0x827c5b5
0x8279da6
0x827ac4f
0x8195096
0x8197900
0x818e8a3
0x818e3dd
0x818d91f
0xed7dd8
0x894d1a

How to repeat:
Cannot be repeated at this time

Could you add the CREATE TABLE statements for the tables involved, or if possible upload table dumps to this bug report. And could you try to resolve the stack trace as documented on http://dev.mysql.com/doc/refman/5.0/en/using-stack-trace.html or let us know the exact distribution packge you are using so that we can resolve the trace for ourselves?

There are references to other tables (entry_type, journal) in your other tables. Can you demonstrate this problem with only one or two tables, without references? Can you just upload dump of all your tables, as private file?

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".