MySQL Bugs: #20162: When doing 'CREATE TABLE...' I get a lost connection to MySQL during query erro

Bug #20162	When doing 'CREATE TABLE...' I get a lost connection to MySQL during query erro
Submitted:	31 May 2006 9:58	Modified:	31 May 2006 15:19
Reporter:	Adrian Aitken	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	4.1.9	OS:	Windows (Windows 2000 server)
Assigned to:	MySQL Verification Team	CPU Architecture:	Any

Description:
Just moved our MySQL database to a new server (HP dual hyper-threaded processor = 4 virtual processors, 2 Gig RAM,Windows 2000 server SP4  etc etc). Loaded existing database fine. Trying via command line "mysql" to create a new table in the database (logged in as root) 
CREATE TABLE `logging` (`Message` CHAR(255));
Crashes the server (have to do a NET START MYSQL) and get a lost connection during query error message. The err.log file just shows me restarting mySQL.

I created a brand new database and tried to create a table in that - same result.

How to repeat:
Try to create the table again !!!

Thank you for the bug report. I was unable to repeat with current release
server 4.1.20. Could you please try with that version:

http://dev.mysql.com/downloads/mysql/4.1.html

If you still have the problem, please provide your my.ini file.

Thanks in advance.

Well it's a bug but not as first thought!!!!!
I managed to create tables by using the TYPE=myISAM command. Searching the my.ini I saw that the default was InnoDB but further down the skip-InnoDB was not hashed out. 
So, it was trying to create an InnoDB table although the .ini said don't use it and rather than exit gracefully it just bombed out the server. Perhaps the next release could make a nice error message instead ?
Regards
Adrian