MySQL Bugs: #19957: can't start query browser due to segmentation fault

Bug #19957	can't start query browser due to segmentation fault
Submitted:	19 May 2006 19:32	Modified:	1 Sep 2006 7:38
Reporter:	David K.	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S3 (Non-critical)
Version:	1.1.18-1	OS:	Linux (Fedora core 5)
Assigned to:		CPU Architecture:	Any

Description:
hello,

i've installed the query browser using the rpm from this site (mysql-query-browser-1.1.18-1.i386.rpm) but i can't even start the query browser on my machine.
when i start, i get the following error:
/usr/bin/mysql-query-browser: line 20:  5138 Speicherzugriffsfehler  $PRG-bin

i've searched for answers but i haven't found a solution at the moment.
can someone tell me what's the problem?

How to repeat:
no repeat

I had problems with QB on SuSE 10.0 too (no matter which binary I tried).
Installing the source RPM did the trick for me.

Have the same problem.

I've build from 1.1.18 under Slackware 10.2 w/ gware.org's Rev.G.

(gcc 3.3.6, glib2-2.8.6. if you need more versions, i can add, but i'm not sure which packages are interesting)

Here's what i get when i try to run mysql-query-browser:

hjb@growing:~/Download/mysql-query-browser/bin$ ./mysql-query-browser
./mysql-query-browser: line 20:  6340 Segmentation fault      $PRG-bin

Here's a backtrace:

(gdb) run
Starting program: /home/hjb/Download/mysql-query-browser/bin/mysql-query-browser-bin
[Thread debugging using libthread_db enabled]
[New Thread -1233295680 (LWP 6360)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1233295680 (LWP 6360)]
0xb760419a in Gtk::Widget::set_sensitive () from /usr/lib/libgtkmm-2.4.so.1

(gdb) bt
#0  0xb760419a in Gtk::Widget::set_sensitive () from /usr/lib/libgtkmm-2.4.so.1
#1  0x0814d8bd in MQBookmarkBrowser::bookmark_select (this=0x83a99a8) at MQBookmarkBrowser.cc:260
#2  0x0814ed18 in sigc::adaptor_functor<sigc::bound_mem_functor0<void, MQBookmarkBrowser> >::operator() (this=0x83b2640) at limit_reference.h:96
#3  0xb706363e in Glib::SignalProxyNormal::slot0_void_callback () from /usr/lib/libglibmm-2.4.so.1
#4  0xb6ebe348 in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0
#5  0xb6eac215 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#6  0xb6ebdcfa in g_signal_emit_by_name () from /usr/lib/libgobject-2.0.so.0
#7  0xb6ebcf3c in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#8  0xb6ebd1c6 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#9  0xb72892af in gtk_tree_selection_unselect_range () from /usr/lib/libgtk-x11-2.0.so.0
#10 0xb729f2a8 in gtk_tree_view_set_model () from /usr/lib/libgtk-x11-2.0.so.0
#11 0xb75f3ddb in Gtk::TreeView::set_model () from /usr/lib/libgtkmm-2.4.so.1
#12 0x08180e99 in MGBrowserList::set_store (this=0x83a9930, store=@0xbf8217e0) at refptr.h:211
#13 0x0814b6ad in MQBookmarkBrowser (this=0x83a9930, bookmarks=0x0) at MQBookmarkBrowser.cc:42
#14 0x0814655e in MQBookmarks (this=0x83a24bc, add_xml=0x0) at MQBookmarks.cc:34
#15 0x080eafe4 in MQMainWindow (this=0x83a2480, win=0x0) at stl_alloc.h:652
#16 0x080eb533 in MQMainWindow::create () at MGGladeXML.h:77
#17 0x080d8e2c in main (argc=1, argv=0xbf821d24) at main.cc:286
(gdb)

I've found out that there was a related bug in the debian bugtracker:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=343632

They say it was fixed by release 1.1.17-5, but it seems to me that 1.1.18 still has the bug.

Thank you for the bug report.

Thank you for your bug report. This issue has already been fixed in the latest released version of that product, which you can download at

  http://www.mysql.com/downloads/