MySQL Bugs: #14338: MySQL server has gone away msg followed by access violation

Bug #14338	MySQL server has gone away msg followed by access violation
Submitted:	26 Oct 2005 17:32	Modified:	22 Nov 2005 16:46
Reporter:	Charles Herrington	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	Connector / ODBC	Severity:	S2 (Serious)
Version:	3.51.12	OS:	Windows (Windows XP)
Assigned to:		CPU Architecture:	Any

Description:
Until recently we have been running MyODBC 3.51.06 because 3.51.11 had issues when dealing with date calculations/comparisons, 3.51.12 seems to have fixed this probem but now I am experiencing random errors loading a recordset followed by an access violation.  Server version is 4.1.12a-nt.

Load Error: -2147217871 Description: [MySQL][ODBC 3.51 Driver][mysqld-4.1.12a-nt]MySQL server has gone away
Data:
0000: 40 9e 1a 00 9c e3 12 00   @..ã..
0008: a6 16 00 11 f4 e1 12 00   ¦...ôá..
0010: 70 11 00 11 00 00 00 00   p.......
0018: 01 00 00 00 f8 e2 12 00   ....øâ..
0020: 1b 00 00 00 b0 e3 12 00   ....°ã..
0028: 50 33 00 11 f0 be 15 00   P3..ð¾..
0030: dc e4 12 00 d8 e4 12 00   Üä..Øä..
0038: 38 e5 12 00 d4 e4 12 00   8å..Ôä..
0040: 74 6c 40 00 00 00 00 00   tl@.....
0048: 43 e9 45 00 74 6c 40 00   CéE.tl@.
0050: 54 e3 12 00 43 e9 45 00   Tã..CéE.
0058: 00 00 00 00 54 e3 12 00   ....Tã..
0060: 05 00 00 00 00 00 00 00   ........
0068: 00 00 00 00 54 e3 12 00   ....Tã..
0070: 2d 38 12 77 54 e3 12 00   -8.wTã..
0078: 00 00 00 00 00 00 00 00   ........
0080: 31 00 30 00 32 00 33 00   1.0.2.3.
0088: 00 00 00 00 00 00 00 00   ........
0090: 90 00 00 00 6f 17 12 77   ...o..w
0098: 00                        .       

How to repeat:
Server: 4.1.12a-nt
MyODBC: 3.51.12

Write a routine that continously reads a recordset until it is stopped and you will get an error.

Hi!

This looks more like a server problem.  Is there any way you can send us a test case that reproduces this problem ?

Thanks

I rolled back to the MyODBC v3.51.06 and it is working fine again so for the moment I am busy testing my software, once I am finished I will set up a test case and see if I can replicate the problem.  In the meantime if there is anything you would like me to check, please let me know.

I have the same bug, well i have the steps to reproduce:

Mysql 4.2
MyOdbc .12

the application must to exec store procedures and return result sets like(the syntaxis is little crap cuz i'm busy in my office):
CREATE PROCEDURE CHECKINGU (city as int)
/** This procedure list contacts in a X city*/
BEGIN
SELECT first_name,last_name FROM CONTACT WHERE city_contact = city;
END

Then u can work with ur application normally and CRASHHH!!!!! the message MYSQL SERVER GONE AWAY appears...

The fact to work with myodbc .12 is the stored procedures and the result set. when i use the .6 version i cant reutrn result set.

hey can u help me?

Best Regards