Bug #20351 | Crash after calling SP | ||
---|---|---|---|
Submitted: | 9 Jun 2006 9:14 | Modified: | 20 Nov 2006 8:21 |
Reporter: | Tonci Grgin | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Query Browser | Severity: | S2 (Serious) |
Version: | 1.1.20 | OS: | Windows (Win XP Pro (SP2)) |
Assigned to: | Mike Lischke | CPU Architecture: | Any |
Tags: | Result Set |
[9 Jun 2006 9:14]
Tonci Grgin
[9 Jun 2006 9:15]
Tonci Grgin
SQL script with data
Attachment: 20084.txt (application/x-download, text), 1.83 KiB.
[9 Jun 2006 9:16]
Tonci Grgin
Screenshot with error
Attachment: 20351.jpg (image/jpeg, text), 69.84 KiB.
[12 Jul 2006 17:55]
Steve Klett
I'm experiencing the same crash and have the same setup. I also have VisualStudio 2005 installed and it appears that is why I get the MS JIT debugger dialog. I choose the debug option. In the output window it's POURING messages like this: First-chance exception at 0x00582e10 in MySQLQueryBrowser.exe: 0xC0000005: Access violation reading location 0x043e1464.
[16 Nov 2006 12:58]
Mike Lischke
Tonci, please try the latest QB version and see if the problem still persists. I cannot reproduce it here.
[20 Nov 2006 7:48]
Tonci Grgin
Mike, you can close it now. Crash no longer occur on same XP box with server version: 5.0.27-log, Source distribution and Querying tool for MySQL Servers 1.2.5.0. I also tested with remote Suse host with 5.0.29BK. All works fine.
[20 Nov 2006 8:21]
Mike Lischke
Excellent. Glad to hear it works now.