3 messages in com.mysql.lists.gui-toolsRE: RH9.0/RH7.3 MysqlCC 0.9.3 beta Se...| From | Sent On | Attachments |
|---|---|---|
| Klaus Friis Østergaard | 21 Nov 2003 05:28 | |
| Adam Hooper | 21 Nov 2003 09:38 | |
| Klaus Friis Østergaard | 24 Nov 2003 06:54 |
| Subject: | RE: RH9.0/RH7.3 MysqlCC 0.9.3 beta Segmentation fault |
|---|---|
| From: | Klaus Friis Østergaard (KF...@LASERTECH.DK) |
| Date: | 11/24/2003 06:54:33 AM |
| List: | com.mysql.lists.gui-tools |
Hi Adam,
Here is the backtrace:
[kfo@Shiraz mysqlcc-0.9.3-src]$ gdb ./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: /home/kfo/tars/mysqlcc-0.9.3-src/mysqlcc [New Thread 1024 (LWP 1009)]
Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1024 (LWP 1009)] 0x4046f853 in QTextCodec::fromUnicode () from /usr/lib/qt-3.0.5/lib/libqt-mt.so.3 (gdb) bt #0 0x4046f853 in QTextCodec::fromUnicode () from /usr/lib/qt-3.0.5/lib/libqt-mt.so.3 #1 0x0810e6f1 in CMySQL::emitError () #2 0x0810e5b3 in CMySQL::connect () #3 0x08097202 in CMySQLServer::connect () #4 0x080bd5f3 in CServerItem::setConnected () #5 0x080bda0f in CServerItem::processMenu () #6 0x080898fe in CDatabaseListView::processCurrentItemMenu () #7 0x081181bd in CDatabaseListView::qt_invoke () #8 0x40233fd7 in QObject::activate_signal () from /usr/lib/qt-3.0.5/lib/libqt-mt.so.3 #9 0x402340fc in QObject::activate_signal () from /usr/lib/qt-3.0.5/lib/libqt-mt.so.3 #10 0x404bdc4d in QPopupMenu::activated () from /usr/lib/qt-3.0.5/lib/libqt-mt.so.3 #11 0x402fd24a in QPopupMenu::actSig () from /usr/lib/qt-3.0.5/lib/libqt-mt.so.3 #12 0x40301a27 in QPopupMenu::keyPressEvent () from /usr/lib/qt-3.0.5/lib/libqt-mt.so.3 #13 0x402608cb in QWidget::event () from /usr/lib/qt-3.0.5/lib/libqt-mt.so.3 #14 0x401ea803 in QApplication::internalNotify () from /usr/lib/qt-3.0.5/lib/libqt-mt.so.3 #15 0x401e9edc in QApplication::notify () from /usr/lib/qt-3.0.5/lib/libqt-mt.so.3 #16 0x4019a378 in QETWidget::translateKeyEvent () from /usr/lib/qt-3.0.5/lib/libqt-mt.so.3 #17 0x40195650 in QApplication::x11ProcessEvent () from /usr/lib/qt-3.0.5/lib/libqt-mt.so.3 #18 0x401945de in QApplication::processNextEvent () from /usr/lib/qt-3.0.5/lib/libqt-mt.so.3 #19 0x401ebcdc in QApplication::enter_loop () from /usr/lib/qt-3.0.5/lib/libqt-mt.so.3 #20 0x40194547 in QApplication::exec () from /usr/lib/qt-3.0.5/lib/libqt-mt.so.3 #21 0x080f9e7a in mysqlcc_main () #22 0x080f7313 in main () #23 0x42017589 in __libc_start_main () from /lib/i686/libc.so.6 (gdb)
This is with the alt+a for action then enter for connect.
When I try to edit a connection, with alt+a and e for edit connection: [Switching to Thread 1024 (LWP 1094)] 0x4046f867 in QTextCodec::fromUnicode () from /usr/lib/qt-3.0.5/lib/libqt-mt.so.3 (gdb) bt #0 0x4046f867 in QTextCodec::fromUnicode () from /usr/lib/qt-3.0.5/lib/libqt-mt.so.3 #1 0x0810e6f1 in CMySQL::emitError () #2 0x0810e5b3 in CMySQL::connect () #3 0x08097202 in CMySQLServer::connect () #4 0x080baaae in CRegisterServerDialog::initConnectionDialog () #5 0x080ba723 in CRegisterServerDialog::CRegisterServerDialog () #6 0x080bda99 in CServerItem::processMenu () #7 0x080898fe in CDatabaseListView::processCurrentItemMenu () #8 0x081181bd in CDatabaseListView::qt_invoke () #9 0x40233fd7 in QObject::activate_signal () from /usr/lib/qt-3.0.5/lib/libqt-mt.so.3 #10 0x402340fc in QObject::activate_signal () from /usr/lib/qt-3.0.5/lib/libqt-mt.so.3 #11 0x404bdc4d in QPopupMenu::activated () from /usr/lib/qt-3.0.5/lib/libqt-mt.so.3 #12 0x402fd24a in QPopupMenu::actSig () from /usr/lib/qt-3.0.5/lib/libqt-mt.so.3 #13 0x40301a27 in QPopupMenu::keyPressEvent () from /usr/lib/qt-3.0.5/lib/libqt-mt.so.3 #14 0x402608cb in QWidget::event () from /usr/lib/qt-3.0.5/lib/libqt-mt.so.3 #15 0x401ea803 in QApplication::internalNotify () from /usr/lib/qt-3.0.5/lib/libqt-mt.so.3 #16 0x401e9edc in QApplication::notify () from /usr/lib/qt-3.0.5/lib/libqt-mt.so.3 #17 0x4019a378 in QETWidget::translateKeyEvent () from /usr/lib/qt-3.0.5/lib/libqt-mt.so.3 #18 0x40195650 in QApplication::x11ProcessEvent () from /usr/lib/qt-3.0.5/lib/libqt-mt.so.3 #19 0x401945de in QApplication::processNextEvent () from /usr/lib/qt-3.0.5/lib/libqt-mt.so.3 #20 0x401ebcdc in QApplication::enter_loop () from /usr/lib/qt-3.0.5/lib/libqt-mt.so.3 #21 0x40194547 in QApplication::exec () from /usr/lib/qt-3.0.5/lib/libqt-mt.so.3 #22 0x080f9e7a in mysqlcc_main () #23 0x080f7313 in main () #24 0x42017589 in __libc_start_main () from /lib/i686/libc.so.6 (gdb)
I hope this gives you usefull information.
/Klaus
-----Original Message----- From: Adam Hooper [mailto:ada...@densi.com] Sent: Friday, November 21, 2003 6:39 PM To: Klaus Friis Østergaard Cc: mysq...@lists.mysql.com Subject: Re: RH9.0/RH7.3 MysqlCC 0.9.3 beta Segmentation fault
Klaus Friis Østergaard wrote:
I get a segmentation fault when I try to connect to Mysql at localhost Mysql is 4.1.0 alpha installed via rpm
When I try to edit the connection I also get a segmentation fault.
I can access mysql via the normal mysql client.
Does any body have a clue on what I am doing wrong?
Kind regards,
Klaus F. Østergaard
If you get a segmentation fault, that means it's not your problem, and the software has a bug.
Try deleting the connection and recreating it, paying very extra-special attention to putting in the right password (it'll segfault on the wrong password).
Beyond that, unless you're willing to help troubleshoot (this will involve compiling from source), there's nothing you can do. If you are, the first step would be to give us a backtrace:
0. Open a console. 1. Run 'gdb /path/to/mysqlcc' where gdb is the GNU debugger (there should be RPMs for it all over the place) and /path/to/mysqlcc is the location of mysqlcc (i.e., /usr/local/bin/mysqlcc or ./mysqlcc or whatever. 2. Type 'r' to run the program. 3. Make it crash. 4. Type 'bt' in your console. 5. Copy all the output here, and email it. 6. Also email the *exact* procedure you use to crash the program. If you can do it without using the mouse, that would be perfect, since a string of keystrokes is easy to repeat. Otherwise, make sure you pay close attention to every single click you make.
-- Adam Hooper ada...@densi.com