Bug #13148 Errors appearing in GRT window about non-existent paths/files

• Submitted: 13 Sep 2005 17:38
• Modified: 16 Apr 2006 13:12
• Reporter: John Zastrow
• Status: No Feedback
• Category: MySQL Workbench Preview
• Severity: S2 (Serious)
• Version: 1.0.1
• OS: Windows (WinXP sp2)
• Assigned to: Mike Lischke
• CPU Architecture: Any

[13 Sep 2005 17:38] John Zastrow

Description:
Open the GRT environment (F4) to see these errors. I unpackaged this release into my f:\ drive.

MySQL Generic Runtime Environment 2.0.10 beta

Type 'help' or '?' for help. Type 'quit' to exit the shell.
Registered 13 struct definition files.
Initializing native loader...
Initializing PHP loader...
Initializing Lua loader...
Registered 3 builtin modules.
Registered 2 PHP modules.
Registered 12 Lua modules.
Registered 1 Workbench module.

file c:\dokumente und einstellungen\mike\eigene dateien\work\mysql-gui-common\library_grt\source\myx_grt_value.c: line 3382: assertion `(list->value.l->content_type == item->type) || (list->value.l->content_type == MYX_ANY_VALUE)' failed
file c:\dokumente und einstellungen\mike\eigene dateien\work\mysql-gui-common\library_grt\source\myx_grt_value.c: line 3382: assertion `(list->value.l->content_type == item->type) || (list->value.l->content_type == MYX_ANY_VALUE)' failed
file c:\dokumente und einstellungen\mike\eigene dateien\work\mysql-gui-common\library_grt\source\myx_grt_value.c: line 3382: assertion `(list->value.l->content_type == item->type) || (list->value.l->content_type == MYX_ANY_VALUE)' failed
file c:\dokumente und einstellungen\mike\eigene dateien\work\mysql-gui-common\library_grt\source\myx_grt_value.c: line 3382: assertion `(list->value.l->content_type == item->type) || (list->value.l->content_type == MYX_ANY_VALUE)' failed
MODEL update TO markers <dict>, model.Marker
/ > 

How to repeat:
Open GRT environment

[16 Mar 2006 13:12] Mike Lischke

Usually these messages are produced if something could not be loaded, read, a file was missing or the folder structure was not as it is required by the tool. Could you please try the latest beta version with its installer? This should ensure everything is in place. As there is also a problem with the installer please install it into the default location and see if that works for you. Please come back here and let me know the outcome.

[16 Mar 2006 20:53] Donald Tyler

I had the same problem and it was caused by the start menu link for MySQL Workbench not having its "Start In" attribute correctly set. Once I fixed that it worked fine.

[28 Mar 2006 20:11] Christophe Gesché

I  come  to confirm comment of Donald Tyler.

In fact If  in installer I chose another directory than default; 

Start in still the default value

[28 Mar 2006 20:12] Christophe Gesché

in 1.0.5

[16 Apr 2006 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".