Hi!
I am seeing this as well. In my case, it occurs after my client
successfully connects to MySQL5.0, retrieves data set via ODBC (libiodbc),
fails to free the statement handle and dumps with the followjng:
*** glibc detected *** double free or corruption (!prev): 0x08259238 ***
Kernel is
Hello!
Is anyone else seeing mysql-server 5.0.18-9 crashing with messages like:
| Mar 14 00:32:59 zwart mysqld[29820]: *** glibc detected *** double
| free or corruption (!prev): 0x012b1ab0 ***
| Mar 15 02:24:17 zwart mysqld[13255]: *** glibc detected *** free():
|
2 matches
Mail list logo