Bug #10698 MySQL-Server crashed on Dual-Opteron-Systems with WinXP SP1
Submitted: 18 May 2005 6:18 Modified: 29 Jun 2005 1:00
Reporter: Jan Kuehl Email Updates:
Status: No Feedback Impact on me:
Category:MySQL Server Severity:S1 (Critical)
Version:4.1.11 and 4.1.8 OS:Windows (Win XP SP1)
Assigned to: CPU Architecture:Any

[18 May 2005 6:18] Jan Kuehl
MySQL server crashed reproducible with MyISAM-Tables on a Dual-Opteron-System (244m, 1,8GHz, 4GB RAM) with WinXP SP1. If the operating system is changed to WinXP 64 the MySQL server works without problems. There exists a special Linux version for AMD64 (Opteron is a 64Bit Processor but not a AMD64) but not a special 64Bit version for WinXP.

The MySQL server crashed during many operation for example creating a database with many tables, selecting some data. 
The memory address is every time the same:
"Unhandled exception at 0x0052dd75 in mysql.exe 0xC0000005: Access violation writing location 0x00000000."
The MS Development Environment disassembly prints the following information:

0052DD60   sub      esp, 8
0052DD63   mov     eax, dword ptr ds: [0075E5A0h]
0052DD68   mov     dword ptr [esp], eax
0052DD6C   mov     ecx, dword ptr [esp]
0052DD70   mov     edx, 1
-> 0052DD75   xchg    edx, dword ptr [ecx]      (point of crash)
0052DD77   mov     dword ptr [esp+4], edx
0052DD7B   mov     ecx, dword ptr [esp+4]
0052DD7F   test     ecx, ecx
0052DD81   je        0052DD96
0052DD83   push    0B0h

Call Stack

Sorry, but we havn't more information about the problem.

How to repeat:
[29 May 2005 1:00] Jorge del Conde

Is there any way you can provide us with a reproducible test case that successfully crashes mysqld ?

Thanks a lot
[29 Jun 2005 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".