Bug #25775 Core dump every time I try to edit a table
Submitted: 23 Jan 2007 9:29 Modified: 24 Apr 2007 14:44
Reporter: Mark Burton Email Updates:
Status: Closed Impact on me:
Category:MySQL Query Browser Severity:S2 (Serious)
Version:1.29rc (and earlier) OS:Linux (linux (SuSE 10.1))
Assigned to: CPU Architecture:Any

[23 Jan 2007 9:29] Mark Burton
The query browsing part of the prog appears to work fine. But if 1 select the "Edit.." option from a table context menu MQB browser crashes. The administrator prog also crashes when I select edit table so there must be some common problem to do with invoking the table editor. My system is a stock SuSE 10.1. Here's a gdb stack trace:

#0  0x0824a2f4 in MGTableEditor::show_table (this=0x8a8ddb8, mysql=0x87e4f00, catalog=@0xbfb4e35c,
    schema=@0xbfb4e358, table=@0xbfb4e354, catalog_data=@0xbfb4e3bc) at MGTableEditor.cc:970
970     MGTableEditor.cc: No such file or directory.
        in MGTableEditor.cc
(gdb) where
#0  0x0824a2f4 in MGTableEditor::show_table (this=0x8a8ddb8, mysql=0x87e4f00, catalog=@0xbfb4e35c,
    schema=@0xbfb4e358, table=@0xbfb4e354, catalog_data=@0xbfb4e3bc) at MGTableEditor.cc:970
#1  0x08220429 in MGSchemaBrowserHelper::edit_table (this=dwarf2_read_address: Corrupted DWARF expression.
) at MGSchemaBrowserHelper.cc:107
#2  0x0822053e in MGSchemaBrowserHelper::edit_object (this=0x880fc90) at MGSchemaBrowserHelper.cc:129
#3  0x08198274 in MQWorkArea::edit_selection (this=0x86fca28) at MQWorkArea.cc:1852
#4  0xb734872a in Glib::SignalProxyNormal::slot0_void_callback () from /opt/gnome/lib/libglibmm-2.4.so.1
#5  0xb71ab599 in g_cclosure_marshal_VOID__VOID () from /opt/gnome/lib/libgobject-2.0.so.0
#6  0xb719e8bd in g_closure_invoke () from /opt/gnome/lib/libgobject-2.0.so.0
#7  0xb71af531 in g_signal_connect_closure_by_id () from /opt/gnome/lib/libgobject-2.0.so.0
#8  0xb71b0ac7 in g_signal_emit_valist () from /opt/gnome/lib/libgobject-2.0.so.0
#9  0xb71b0c95 in g_signal_emit () from /opt/gnome/lib/libgobject-2.0.so.0
#10 0xb75ab9e4 in gtk_widget_activate () from /opt/gnome/lib/libgtk-x11-2.0.so.0
#11 0xb74c8aa8 in gtk_menu_shell_activate_item () from /opt/gnome/lib/libgtk-x11-2.0.so.0
#12 0xb74ca022 in gtk_menu_shell_append () from /opt/gnome/lib/libgtk-x11-2.0.so.0
#13 0xb74be66f in gtk_menu_attach () from /opt/gnome/lib/libgtk-x11-2.0.so.0
#14 0xb78e51cd in Gtk::Widget_Class::button_release_event_callback ()
   from /opt/gnome/lib/libgtkmm-2.4.so.1
#15 0xb74bcbee in gtk_marshal_BOOLEAN__VOID () from /opt/gnome/lib/libgtk-x11-2.0.so.0
#16 0xb719d0c7 in g_value_set_static_boxed () from /opt/gnome/lib/libgobject-2.0.so.0
#17 0xb719e8bd in g_closure_invoke () from /opt/gnome/lib/libgobject-2.0.so.0
#18 0xb71af893 in g_signal_connect_closure_by_id () from /opt/gnome/lib/libgobject-2.0.so.0
#19 0xb71b088f in g_signal_emit_valist () from /opt/gnome/lib/libgobject-2.0.so.0
#20 0xb71b0c95 in g_signal_emit () from /opt/gnome/lib/libgobject-2.0.so.0
#21 0xb75a78d8 in gtk_widget_get_default_style () from /opt/gnome/lib/libgtk-x11-2.0.so.0
#22 0xb74b6603 in gtk_propagate_event () from /opt/gnome/lib/libgtk-x11-2.0.so.0
#23 0xb74b7857 in gtk_main_do_event () from /opt/gnome/lib/libgtk-x11-2.0.so.0
#24 0xb72d258a in gdk_add_client_message_filter () from /opt/gnome/lib/libgdk-x11-2.0.so.0
#25 0xb712fabd in g_main_context_dispatch () from /opt/gnome/lib/libglib-2.0.so.0
#26 0xb7132cbf in g_main_context_check () from /opt/gnome/lib/libglib-2.0.so.0
#27 0xb7133069 in g_main_loop_run () from /opt/gnome/lib/libglib-2.0.so.0
#28 0xb74b7cd4 in gtk_main () from /opt/gnome/lib/libgtk-x11-2.0.so.0
#29 0xb78812c7 in Gtk::Main::run_impl () from /opt/gnome/lib/libgtkmm-2.4.so.1
#30 0xb78810b2 in Gtk::Main::run () from /opt/gnome/lib/libgtkmm-2.4.so.1
#31 0x08152d3c in main (argc=137704400, argv=0xb6db0000) at main.cc:343

How to repeat:
Attempt to edit a table!
[23 Jan 2007 14:34] MySQL Verification Team
Thank you for the bug report. Could you please provide the table definition
(create table command) which is able to provoke that behavior on your side.
I was unable to repeat on Ubuntu 6.10. Thanks in advance.
[23 Jan 2007 14:46] Mark Burton
i have uploaded a file of table definitions - I cannot edit these due to the reported bug.

FYI - the database is hosted on a remote machine (mysql 4.0.23a)
[24 Jan 2007 12:44] Mark Burton
One other thing I have just noticed with this release is that I can no longer edit  the results of a query. The tables I uploaded yesterday I could previously edit using the QB but with this release the editing buttons are no longer enabled for these tables.
[24 Jan 2007 15:59] Wesley Hampton
Hi Mark, I can confirm not being able to edit queries on SuSE 10.2 with rc9 Query Browser.  I installed the new rc9 GUItools yesterday and started having this problem.  Previously I had rc8 installed.  Hope this helps.

[24 Jan 2007 18:00] Wesley Hampton
Sorry, just to be clear, I cannot edit the RESULTS of any queries in rc9 Query Browser when I could edit those same results with rc8 and previous releases. The "Start Editing" button at the lower right corner never becomes active.
[24 Jan 2007 18:09] Mark Burton
Hi Wesley,

Yes, it's the same for me. The QB doesn't want me to edit the data even though it did in a previous release.

I also have the added problem of not being able to edit the table definition without the QB blowing up (my original bug). Can you edit the table definitions using the QB?

[25 Jan 2007 12:40] Wesley Hampton
Hey Mark, oddly I can edit tables, unlike you!  I was able to create a table in the `test` DB with three fields (int, text, datetime) and save.  Then I was able to edit the table, rename fields, change data types, change the storage engine, and rename the table successfully.  The actual DB is on another server and is running MySQL 5.0.22 on a Win2k server.  Let me know if you want me to try anything else.
[8 Feb 2007 11:59] Tim Salter
Cannot edit data? I found that if you remove the backquotes from the schema name and/or table name, re-execute the query, the reccords then become editable (unless it crashes first of course).
[12 Feb 2007 12:48] Wesley Hampton
Hmmm, well when I remove the little backticks I still cannot edit the results of queries.
[12 Feb 2007 17:36] Michael Reeves
Wesley pointed me to your discussion.

If you'd like to move the discussion of Editing the Query Results over to a seperate bug, it's at

I've been experiencing the same thing on RHEL 4.

I haven't had any problems with editing the table definitions though.
[13 Feb 2007 19:48] Tim McCalmant
I am having the same problem on Fedora Core 6. I am running Query Browser version 1.1.18 and it, as well, crashes every time I try and edit a table. I have tried copying the database to my local machine to see if that makes a difference but it did not. The other guys in my IT department are running Fedora Core 5 with the same version of MySQL and it works just fine for them. Interesting...
[24 Apr 2007 14:30] MySQL Verification Team
Please try with version 1.2.11 I am not able to repeat with this version.
[24 Apr 2007 14:38] Mark Burton
Yes, version 1.2.11 seems to work OK - I can edit tables.
[24 Apr 2007 14:44] MySQL Verification Team
Thank you for the feedback.