MySQL Bugs: #1205: Crashes every time it tries to connect

Bug #1205	Crashes every time it tries to connect
Submitted:	5 Sep 2003 10:02	Modified:	8 Dec 2003 16:02
Reporter:	[ name withheld ]	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQLCC	Severity:	S2 (Serious)
Version:	0.9.3	OS:	Windows (xp)
Assigned to:	Jorge del Conde	CPU Architecture:	Any

Description:
I get the following every time I try to connect to MySql 4.0.14b with XP.  It works fine when connecting to 3.23.

Faulting application mysqlcc.exe, version 0.0.0.0, faulting module qt-mt312.dll, version 0.0.0.0, fault address 0x001e1141.

How to repeat:
Setup a connection to a 4.0.14b running both server and client on XP.  I get the same error doing multiple things with that conneciton.

I am also having the same issue on a Win98 client -> mysqlcc-0.9.3-win32.zip
I have managed to actually create an entry (for a database), but onkly after many crashes.  I can not use the entry, even editing it has so far brought nothing but fatals...

I am not a C++ programmer, but I do a lot of DBA work.  My tool of choise is MySql.  The only thing holding most of my clients back is a good GUI like CC.  I will do anything I can to help you get this going so as to replace MS SQL Server on my clients systems.  By replacing that DB, I also get to replace the OS (WIN2000 in most cases) and greatly reduce my workload for administering and worrying about their systems!   BTW - Thanks for MySql!

SERVER 1:
[root@12-223-133-42 /root]# mysql -V
mysql  Ver 11.13 Distrib 3.23.36, for redhat-linux-gnu (i386)

CLIENT 1:  Illegal Operation warning in Win98 when trying to test settings of connection
MYSQLCC caused an invalid page fault in
module QT-MT312.DLL at 0177:39ee1143.
Registers:
EAX=0074f420 CS=0177 EIP=39ee1143 EFLGS=00010202
EBX=00000000 SS=017f ESP=0074f3f4 EBP=0074f404
ECX=0093410c DS=017f ESI=0074f410 FS=590f
EDX=00000011 ES=017f EDI=008bedc0 GS=0000
Bytes at CS:EIP:
ff 52 20 8b 45 08 5e 5d c2 08 00 55 8b ec 8b 45 
Stack dump:
0074f418 0074f420 0074f410 008c3270 0074f428 004033d5 0074f418 00000049 00934a20 00934790 00935ee0 009349d0 0074f4a0 0074f4a0 00403305 00935ee0 

CLIENT 1: Illegal Operation warning in Win98 when trying to edit settings of server.
MYSQLCC caused an invalid page fault in
module QT-MT312.DLL at 0177:39ee1143.
Registers:
EAX=0074eb28 CS=0177 EIP=39ee1143 EFLGS=00010202
EBX=00000000 SS=017f ESP=0074eafc EBP=0074eb0c
ECX=008e7b3c DS=017f ESI=0074eb18 FS=0e3f
EDX=000000c0 ES=017f EDI=00907170 GS=0000
Bytes at CS:EIP:
ff 52 20 8b 45 08 5e 5d c2 08 00 55 8b ec 8b 45 
Stack dump:
0074eb20 0074eb28 0074eb18 008fc440 0074eb30 004033d5 0074eb20 00000049 008e6690 008e1630 008e5f60 008e04f0 0074eba8 0074eba8 00403305 008e5f60

Please verify if the crash is happening because there is an invalid
password or user name in the connection data. 

Also this should happen if there are wrong values for port number and
socket file path. So please before to try the connect right click the
connection name and select edit. verify the data and change them if
necessary.

If the above is true then this bug report will be marked as duplicate
of bug #1368.

I have gone through my settings.  The username, password and port are all correct (and tested with mysql command from another linux box).  I visually checked for the socket and it is where it is supposed to be.  The command 'mysqladmin variables' shows all the values to be correct.
| socket                  | /var/lib/mysql/mysql.sock 
| version                 | 3.23.36 
| port                    | 3306 
...

-Bill

Please ignore the previous post.  I forgot to check the addresses in the user table to ensure access for the user was allowed from the remote machines.

It works now.

Again, thanks for your great product.

-Bill

I've got the same bug (I accidently opened a duplicate sorry, don't know how to close it #1380).  Because I was trying to connect to a server that wasn't available.  When I redirected to my local test server it then crashed again because I had the wrong password.  However when I corrected this it worked fine.

Ok, I also created a duplicate bug for this issue. I am a novice here - mine problem is pretty clearly coming from a name/password error - but I have no idea how to fix it in the application. I thought I set things up fine through the command line interface, but I still cannot access it through the control center. Any help here would be appreciated.

Thanks!

On a second thought - my username/password must be correct since I am able to use it in my application and all of my queries and db access are fine. What else could be the problem? This problem occurs only moments after the application launches - I assume it is trying to auto connect to the db, but failing. Since I immediately get a microsoft report error, it is impossible for me to do anything through the control center UI.

Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html