Bug #15226 | Administrator crash | ||
---|---|---|---|
Submitted: | 24 Nov 2005 14:17 | Modified: | 6 Dec 2005 3:38 |
Reporter: | Jan Buchholz | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Administrator | Severity: | S2 (Serious) |
Version: | 1.1.4 | OS: | MacOS (Mac OSX 10.4.3) |
Assigned to: | Alfredo Kojima | CPU Architecture: | Any |
[24 Nov 2005 14:17]
Jan Buchholz
[1 Dec 2005 22:38]
Alfredo Kojima
I am not able to reproduce it (also there is no 1.1.4 version for Mac OS X yet, but I assume you meant 1.1.0). Please look at ~/Library/Logs/CrashReporter/ for the file corresponding to Administrator and attach to this report.
[2 Dec 2005 15:43]
Mike Austin
I'm having the same problem: Version: 1.1.4 System: Windows XP
[2 Dec 2005 15:47]
Mike Austin
Sorry.. I mean 1.1.0 of the administrator also. It also happens with the query browser. The MySQL service crashes and I am unable to edit tables or stored procedures. This started happening when I added my first stored procedure.
[3 Dec 2005 15:41]
Jan Buchholz
Crashlog (from popup)
Attachment: Crash_MySQLAdmin.txt (text/plain), 16.42 KiB.
[3 Dec 2005 15:44]
Jan Buchholz
Crash Log from "logs" directory (zipped)
Attachment: MySQL Administrator.crash.log.zip (application/zip, text), 8.77 KiB.
[3 Dec 2005 15:46]
Jan Buchholz
To reproduce the error you need to create a stored function (NOT procedure) that returns a CHAR(50) or similar. As long as the return parameter is of type INT, MySQL Admin won't crash.
[6 Dec 2005 3:38]
Alfredo Kojima
Thank you, with that info I was able to reproduce the bug. Version 1.1.2 should have that fixed. Unfortunately 1.1.1 was already closed, but we'll probably release 1.1.2 shortly.