Bug #37561 MySQL WorkBench 5.0
Submitted: 20 Jun 2008 22:59 Modified: 30 Jun 2008 12:33
Reporter: Thomas McLaughlin Email Updates:
Status: Can't repeat Impact on me:
Category:MySQL Workbench Severity:S3 (Non-critical)
Version: OS:Windows (XP)
Assigned to: CPU Architecture:Any
Tags: diff, Generate, report, schema

[20 Jun 2008 22:59] Thomas McLaughlin
To Whom IT May Concern:

We are receiving the following error from Module Name msvcr80.dll when we try to get the differences in the schema between two databases on different live server. It reports the offset as 00008a8c.

Error report contents:

Code: 0xc000000d  Flags: 0x0000000
Record: 0x0000000000000000  Address:  0x0000000078138aBc

System Information
Windows NT 5.1 Build: 2600
CPU Vendor Code:  756E6547 - 49656E69 - 6C65746E
CPU Version: 00000F43  CPU Feature Code: BFEBFBFF
CPU AMD Feature Code: 00D6E824

Module 1
Image Base: 0x00400000   Image Size:  0x00000000
Checksum:  0x00000000    Time Stamp:  0x483abe21

Version Information
 Signature: feef04bd
 StrucVer:  00010000
 FileVer:   (5.0:22.3118}
 ProdVer:   (5.0:22.3118}
 FlagMask:  0000003f
 Flags:     00000000
 OS:        00000004
 FileType:  00000001
 SubType:   00000000
 FileDate:  00000000:00000000

I can send a screen shot with the rest of the information. 

How to repeat:
On our Windows XP system use MySQL Workbench Standard Edition select under databases select Generate Schema Diff Report and connect to a MySQL 5 database called "gttx" on SUSE Linux server and select another database called "staginggttx" on a SUSE Linux server. When you try to generate the Schema Diff Report the above error is generated.
[21 Jun 2008 16:05] MySQL Verification Team
Thank you for the bug report. Verified with live server Fedora Core 8 and live server XP (the same running the WorkBench tool).
[30 Jun 2008 12:33] MySQL Verification Team
I tested now with version 5.0.23 and I could not repeat. Could you please upgrade and try again. Thanks in advance.
[30 Jun 2008 12:37] Vladimir Kolesnikov
If you still can reproduce the bug with 5.0.23 please attach a sample database dump that can be used to reproduce he problem (you can attach the files privately, so nobody except developers can access it).