Bug #1971 Segmentation fault when editing a connection
Submitted: 27 Nov 2003 8:40 Modified: 8 Dec 2003 16:31
Reporter: Klaus Østergaard Email Updates:
Status: Closed Impact on me:
Category:MySQLCC Severity:S1 (Critical)
Version:0.9.3 bet OS:Linux (RH 7.3/RH9.0)
Assigned to: CPU Architecture:Any

[27 Nov 2003 8:40] Klaus Østergaard
When I try to edit a connection i get a segmentation fault.

I have checked that the mysqlserver is running and I can connect to it with mysql (the client)

Using following steps to reproduce the bug

start mysqlcc

alt+a for action
e for edit -> segmentation fault

I have tried it under gdb and below is a backtrace.

I hope this can help


[kfo@Shiraz scripts]$ gdb /usr/local/mysqlcc/mysqlcc 
GNU gdb Red Hat Linux (5.2-2)
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux"...
(gdb) r
Starting program: /usr/local/mysqlcc-0.9.3-linux-glibc22/mysqlcc 
[New Thread 1024 (LWP 8457)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1024 (LWP 8457)]
0x083b739a in QTextCodec::fromUnicode(QString const&) const ()
(gdb) bt
#0  0x083b739a in QTextCodec::fromUnicode(QString const&) const ()
#1  0x0812844c in CMySQL::emitError() ()
#2  0x081281fd in CMySQL::connect() ()
#3  0x080a4a71 in CMySQLServer::connect() ()
#4  0x080cb6b4 in CRegisterServerDialog::initConnectionDialog(CMessagePanel*) ()
#5  0x080cb120 in CRegisterServerDialog::CRegisterServerDialog(QString const&, CMessagePanel*, QWidget*) ()
#6  0x080cef7e in CServerItem::processMenu(int) ()
#7  0x08091acf in CDatabaseListView::processCurrentItemMenu(int) ()
#8  0x0812ffe8 in CDatabaseListView::qt_invoke(int, QUObject*) ()
#9  0x081e5de9 in QObject::activate_signal(QConnectionList*, QUObject*) ()
#10 0x081e5e94 in QObject::activate_signal(int, int) ()
#11 0x083e82ae in QPopupMenu::activated(int) ()
#12 0x08298822 in QPopupMenu::actSig(int, bool) ()
#13 0x0829d685 in QPopupMenu::keyPressEvent(QKeyEvent*) ()
#14 0x081fe0a1 in QWidget::event(QEvent*) ()
#15 0x0819ff0b in QApplication::internalNotify(QObject*, QEvent*) ()
#16 0x0819fb28 in QApplication::notify(QObject*, QEvent*) ()
#17 0x0815913b in QETWidget::translateKeyEvent(_XEvent const*, bool) ()
#18 0x081557ee in QApplication::x11ProcessEvent(_XEvent*) ()
#19 0x083f515f in QEventLoop::processEvents(unsigned) ()
#20 0x081ac753 in QEventLoop::enterLoop() ()
#21 0x081ac620 in QEventLoop::exec() ()
#22 0x081a00b7 in QApplication::exec() ()
#23 0x080e0b6e in mysqlcc_main(int, char**) ()
#24 0x080e22bf in main ()
#25 0x42017589 in __libc_start_main () from /lib/i686/libc.so.6

How to repeat:
start mysqlcc

alt+a for action
e for edit -> segmentation fault

Suggested fix:
[28 Nov 2003 7:18] Dean Ellis
This is very probably a duplicate of a known and reported issue where MySQLCC 0.9.3 crashes on connection failure.  You can remove or edit the connection in ~/.mysqlcc/connections if this is the case.

Thank you.
[8 Dec 2003 16:31] Jorge del Conde
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at