MySQL Bugs: #34918: Execution of incorrect SQL in client leads to a loud beep and system shutdown

Bug #34918	Execution of incorrect SQL in client leads to a loud beep and system shutdown
Submitted:	28 Feb 2008 6:53	Modified:	2 May 2008 10:11
Reporter:	John Nash	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: Command-line Clients	Severity:	S1 (Critical)
Version:	5.0	OS:	Windows (XP Professional)
Assigned to:		CPU Architecture:	Any
Tags:	loud beep, system shutdown

Description:
I have successfully installed MySQL Server on my laptop for developmental purpose. From the command client, I am able to connect to the server and issue commands. But if the commands are incorrect or out of scope (eg. Select * from databases;), as soon as I execute by pressing 'Enter' key, I get a loud beep and the system crash, that is, the system shutdown abruptly. This happens everytime there is a SQL query is incorrect. I am puzzled as to the nature of the poor implementation of the failsafe scenario in MySQL. Could someone, throw more light on this! I am using the latest version of MySQL 5.0. Please help!

How to repeat:
Type any incorrect or out of scope SQL query in Command client.

Thank you for a problem report. What exact version, 5.0.x, do you use?

I am not able to get anything similar to what you described:

C:\Program Files\MySQL\MySQL Server 5.0\bin>mysql -uroot -proot -P3308 test
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 31
Server version: 5.0.56-enterprise-gpl-nt MySQL Enterprise Server (GPL)

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> select * from databases;
ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that
corresponds to your MySQL server version for the right syntax to use near 'datab
ases' at line 1

So, just error message.

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".

John,

we still need to know which exact version you installed. You can get this informations by using:

mysql> select version();

Also we need to know which client do you use? Do you use MySQL CLI? CLI is the client that you will have on your "cmd".

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".