Bug #113759 Program crashes when I try to access the reverse engineering tab
Submitted: 25 Jan 12:15 Modified: 25 Jan 13:58
Reporter: Ore Gbadebo Smith Email Updates:
Status: Can't repeat Impact on me:
Category:MySQL Server Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: CPU Architecture:Any

[25 Jan 12:15] Ore Gbadebo Smith
Exception Type: The crash was caused by an EXC_BAD_ACCESS (SIGSEGV) exception. This type of exception typically indicates that the application tried to access a memory address that it wasn't allowed to. Specifically, the error was a KERN_INVALID_ADDRESS at 0x00000000000000e0. This suggests the program attempted to access or dereference a null or invalid pointer.
Crashed Thread: The crash occurred in Thread 0, which was the main execution thread of the application.
Call Stack: The most crucial part of the crash report is the call stack at the time of the crash, which can provide insights into what the application was doing when it crashed. The key functions in the stack trace include:
mforms::ToolBar::find_item(...): This function in libmforms.dylib seems to be the direct cause of the crash. It was attempting to find an item in a toolbar when the crash occurred.

How to repeat:
I dont kn
[25 Jan 12:15] Ore Gbadebo Smith
How to repeat try to access the reverse engineer tab.
[25 Jan 13:58] MySQL Verification Team
Hi Mr. Smith,

Thank you very much for your bug report.

First of all, we do not have a version of

Second and much more important. This is a forum for the bug reports, but only for those with fully repeatalbe test cases. If the Category for the bug is "MySQL Server", then the entire test case has to be  written in pure SQL and specifically in the variant that our server supports.

Since you have not provided a test case, we can not proceed with your report.

Can't repeat.