Bug #1910 | Application crashes when I attempt to connect to a remote server | ||
---|---|---|---|
Submitted: | 21 Nov 2003 12:59 | Modified: | 8 Dec 2003 16:28 |
Reporter: | Robert Brown III | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQLCC | Severity: | S1 (Critical) |
Version: | 0.9.3 | OS: | Windows (Windows 2000) |
Assigned to: | CPU Architecture: | Any |
[21 Nov 2003 12:59]
Robert Brown III
[21 Nov 2003 13:07]
Robert Brown III
Another piece of information: The "silent" exit occurrs on Windows 2000 Server. On Windows 2000 Professional, you get the following message during the crash: the instruction at "0x39ee141" referenced memory at "0x7463656c". The memory could not be "read". Press OK to terminate the program Press CANCEL to debug the program
[21 Nov 2003 13:35]
Dean Ellis
Verify that you are providing the correct login information; also you may wish to try using another tool (the mysql command-line client, for instance) to verify that you can actually connect. There is a known and already reported issue with 0.9.3 where connection failures cause MySQLCC to crash. Thank you
[8 Dec 2003 16:28]
Jorge del Conde
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