Bug #26896 MySQL Administrator crashes when attempting to create a new schema
Submitted: 7 Mar 2007 4:50 Modified: 7 Mar 2007 5:38
Reporter: Justin Sullard Email Updates:
Status: Duplicate Impact on me:
Category:MySQL Administrator Severity:S1 (Critical)
Version:1.2.10ga OS:MacOS (Mac OS X 10.4.8)
Assigned to: CPU Architecture:Any
Tags: administrator, crash, libmysqlx.a, os x, osx, schema

[7 Mar 2007 4:50] Justin Sullard
When attempting to create a new schema using MySQL Adminstrator a fatal error occurs and the application crashes. Attaching a debugger to the problem results in the following output:

Exception:  EXC_BAD_ACCESS (0x0001)
Codes:      KERN_PROTECTION_FAILURE (0x0002) at 0x925f941d

Reading symbols for shared libraries .......... done
/Users/my_user_name/22082: No such file or directory.
Attaching to program: `/Applications/Utilities/MySQL Tools/MySQL Administrator.app/Contents/MacOS/MySQL Administrator', process 22082.
Reading symbols for shared libraries ................................................................++... done
0x90009857 in mach_msg_trap ()
warning: Could not open OSO archive file "/Users/vlad/guibuild/Development/libmysqlx.a"
/System/Library/CoreServices/Crash Reporter.app/Contents/Resources/gdb-continue-script:4: Error in sourced command file:
Couldn't open object file '/Users/vlad/guibuild/Development/libmysqlx.a(myx_query.o)'

How to repeat:
Restart the application, reconnect to mySQL server, and attempt to create a new schema

Suggested fix:
From what I can tell there may have been a resource that was not included in the final build for this application, 'libmysqlx.a'. From what I can tell this is either an assembled source code for OS X or a Pascal Archive file, probably the first. Resolving this issue may be as simple as rebuilding the application with the 'libmysqlx.a' source included in the build. Other than that I am unsure what may be done to resolve the problem.
[7 Mar 2007 5:38] Valeriy Kravchuk
Please do not submit the same bug more than once. An existing bug report, bug #26816, already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely to be the same. Because of this, we hope you add your comments to the original bug instead.

Thank you for your interest in MySQL.