MySQL Bugs: #14731: mysqld.exe crashes on DROP / CREATE PROCEDURE

Bug #14731	mysqld.exe crashes on DROP / CREATE PROCEDURE
Submitted:	8 Nov 2005 8:17	Modified:	10 Nov 2005 1:12
Reporter:	Bugs System	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	5.0.15	OS:	Windows (Windows XP)
Assigned to:		CPU Architecture:	Any

Description:
Sometimes while handling with DROP PROCEDURE / CREATE PROCEDURE queries the mysqld.exe crashes with an access violation "cannot read from 000000000".

Unfortunately I'm unable to offer a reproduceable procedure.

Are you interessed to get bug messages like this - without a reproducable procedure?

How to repeat:
???

Have you "use" any database before trying to execute CREATE PROCEDURE? (If no it may be a known problem).

We really need a text of procedures to DROP/CREATE and, at least, a description of situation when this crash occurs. 

As for the repeatable test case, yes, as you already know, it is desirable. If neither you, nor any support engineer will be able to create it, the report is almost useless (for MySQL AB, at least).

Ok, sounds you are not interessted to fix bugs while we don't tell you how to reproduce.

We resepct that you accept hard crashes like this - but it's your decision...

PS
While you are not interessed about bugs like this we're not interessed to help you with bugs like this. ;-)

Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at
http://bugs.mysql.com/how-to-report.php

If you can provide more information, feel free to add it
to this bug and change the status back to 'Open'.

Thank you for your interest in MySQL.

Additional info:

I asked you a question. You do not want to answer, do not want to provide any additional information... OK. What shell I do with this report? I have no Cristall Ball at hand, and have no time to guess...

Yes, there are many cases when SPs crash the server. Check the existing bug report, http://bugs.mysql.com/bug.php?id=14248, for example. That bug is fixed  in 5.0.16. Wait for the release and try you misterious actions once more.

This is the last useful thing I can tell you on this issue.

The bug message Valeriy don't want to hunt

Attachment: MySQL-Error.gif (image/gif, text), 7.18 KiB.

I've attached a screenshot of the bug Valeriy is not interessed to hunt.

Sorry, but while you are don't try to hunt and fix crashes like this there is no reason to report any other bugs to you...

OK. If the only problem is me not wanting to hunt this bug, let anybody else do it. 

Any ideas on how to repeat this bug or when it usually occures are welcomed, as always.

Hihi, nice joke!!! :-)))

You ask again about our help. You please again me to do YOUR work! Seems you are not able to understand: It's your job to hunt and fix the bugs. It's really not our job. It's also not our job to make any test or something like that.

If you want our help about futher bug reports please re-check all bug we reported to you. After the fix of all bugs you can inform us - we will report further bugs to you. But we will not help you further more before...