Bug #20999 | "Memory could not be read" exception | ||
---|---|---|---|
Submitted: | 12 Jul 2006 12:16 | Modified: | 14 Jul 2006 14:33 |
Reporter: | Sudarsh E A | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Query Browser | Severity: | S1 (Critical) |
Version: | 1.1.20 | OS: | Windows (Windows XP Pro) |
Assigned to: | CPU Architecture: | Any | |
Tags: | error, query browser |
[12 Jul 2006 12:16]
Sudarsh E A
[12 Jul 2006 12:30]
Valeriy Kravchuk
Thank you for a problem report. Please, sepecify the exact CREATE PROCEDURE, version of MySQL server used, and address of that exception.
[12 Jul 2006 12:34]
Sudarsh E A
-
[12 Jul 2006 13:27]
Sudarsh E A
Sql Server Version 5.0 procedure creation version : Don't Know (Created through same Query Browser) procedure example ----------------- CREATE DEFINER=``@`%` PROCEDURE `SELECT_COUNTRY`() BEGIN SELECT * FROM CountryMaster; END Exception Dump: The instruction at "0x00582e10" referenced memory at "0x02575dbc". Exception EAccessViolation in module MySQLQueryBrowser.exe at 00182E10. Read of address 02576D80 Exception EOSError in Module MySQLQueryBrowser.exe at 000108D6. System Error. Code:5. Runtime Error 216 at 00403E1A
[12 Jul 2006 17:16]
Valeriy Kravchuk
Thank you for the additional information. Version 5.0 for server is not enough, though. I need exact one, 5.0.x. Is it 5.0.20?
[13 Jul 2006 16:25]
Sudarsh E A
Exact MySql Server version is 5.0.21
[14 Jul 2006 9:14]
Bogdan Enache
Probably same as bug #21000 ?
[14 Jul 2006 14:33]
Sudarsh E A
Success ! Thank you.