Details
Major
Description
When I mess up an sql statement the command line client goes berserk.
Steps to reproduce.
1. Open a windows command line.
2. cd to the location of mysql.exe
3. run mysql.exe
4. type an invalid command like "show tables;" without selecting a database first.
At this point I have to reboot.
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Note: Removing the audio drivers has no effect. Still crashes without the --no-beep option.
I would love a patch. However I have reduced this problem to an exterior problem with the PC speaker. I was following the instructions here http://www.ehow.com/how_5775259_disable-internal-speaker-dell-laptop.html and when tried step 2. it crashed in the exact same way.
Could you give attached mysql.exe a test? The beep is produces with a different API, and should actually make a Windows sound, rather than make one using system speakers
I think your fix would have fixed it for the broken state of my computer. I am sorry but I fixed the original problem thus everything works now. I like your fix much more than the original. Thank you very much for helping me find the root of the problem and for getting away from that dam system bell.
I had to restore my computer to factory settings and re install everything. The previous user screwed the computer royally.
Hi,
Could you please be a bit more specific:
I just tried 5.5.27 on XP 32-bit and 5.5.29 on Win7 64-bit; in both cases I'm getting a text error message and a beep (an annoying one, I must agree, but that's expected). Nothing hangs, nothing crashes.