| Bug #24045 | Crushes on attempted connection on AMD64 and probably other 64-bit platforms | ||
|---|---|---|---|
| Submitted: | 7 Nov 2006 15:20 | Modified: | 9 Jan 2007 15:19 |
| Reporter: | [ name withheld ] | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Query Browser | Severity: | S2 (Serious) |
| Version: | 1.2.6 beta, 1.2.5beta | OS: | Linux (Debian/Linux) |
| Assigned to: | Alfredo Kojima | CPU Architecture: | Any |
[7 Nov 2006 15:20]
[ name withheld ]
[25 Nov 2006 9:21]
Valeriy Kravchuk
Thank you for a problem report. Please, try to repeat with a newer version, from GUI Tools 5.0r6, and inform about the results.
[26 Dec 2006 0:00]
Bugs System
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".
[26 Dec 2006 1:09]
[ name withheld ]
Further information from Casey Zacek from Debian bug list: "You can connect to a remote server just fine. The problem is selecting a schema (database). If you specify the schema on the connection screen, it does this at connection time, and the segfault is immediate. Also note that the binary bundled in mysql-gui-tools-5.0r6-linux-x86_64.tar.gz downloaded from mysql.com exhibits the same exact behavior."
[30 Dec 2006 8:15]
Valeriy Kravchuk
Please, try to repeat with a newer version, from GUI Tools 5.0r8, and inform about the results.
[5 Jan 2007 16:24]
[ name withheld ]
Got the user to try it with the r8 version. From the Debian bug report, -------------------- > Could you please try to duplicate this error with mysql-query-browser > > from version 5.0r8 ? > > > > http://dev.mysql.com/get/Downloads/MySQLGUITools/mysql-gui-tools-5.0r8-linux-x86_64.tar.gz... ./mysql-query-browser: line 103: 5327 Segmentation fault (core dumped) $PRG-bin $args sigh. -- Casey Zacek Senior Engineer NeoSpire, Inc.
[9 Jan 2007 15:19]
Alfredo Kojima
Although it was related to a bad typecast, somehow the bug only showed when connecting to a MySQL 4.x server. It has been fixed now, thanks for the report.
