mysqlcc segmentation fault

[dimulescu]

Hello,

I have emerged mysqlcc (QT application) twice and it keeps segfaulting... It only crashes if I run it at normal user; if I run it as root, it works.

Here is the backtrace I get if I run it in the debugger:

GNU gdb 5.3
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 "i686-pc-linux-gnu"...(no debugging symbols found)...
(gdb) r
Starting program: /usr/bin/mysqlcc
(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New Thread 16384 (LWP 5952)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 5952)]
0x406baa87 in QTextCodec::fromUnicode(QString const&) const () from /usr/qt/3/lib/libqt-mt.so.3
(gdb) where
#0 0x406baa87 in QTextCodec::fromUnicode(QString const&) const () from /usr/qt/3/lib/libqt-mt.so.3
#1 0x0815b98f in QMap<QString, QString>::operator[](QString const&) ()
#2 0x0815b6cc in QMap<QString, QString>::operator[](QString const&) ()
#3 0x080b2db4 in QPtrList<QWidget>::deleteItem(void*) ()
#4 0x080ea4c9 in QMapIterator<QString, QString>::inc() ()
#5 0x080ea465 in QMapIterator<QString, QString>::inc() ()
#6 0x0813c0e1 in QValueList<QString>::detach() ()
#7 0x0813c8e6 in QValueList<QString>::detach() ()
#8 0x0813d2ef in QValueList<QString>::detach() ()
#9 0x0813b0f3 in QValueList<QString>::detach() ()
#10 0x40a717a7 in __libc_start_main () from /lib/libc.so.6
(gdb)

I now remember that when I first installed Gentoo, as I kept my initial .bash_profile I had the same problem with all programs (ls included). No command worked until I erased my old .bash_profile (which contained all kinds of variable settings)

I guess this is all about an environment problem. Maybe the wrong library gets found at runtime ? Here is my environment.

Thank you for any ideas!

dadi@kati openreports $ set
BASH=/bin/bash
BASH_VERSINFO=([0]="2" [1]="05b" [2]="0" [3]="1" [4]="release" [5]="i686-pc-linux-gnu")
BASH_VERSION='2.05b.0(1)-release'
CC=gcc
CLASSPATH=/opt/blackdown-jdk-1.4.1/jre/lib/rt.jar:.
COLORTERM=
COLUMNS=113
CONFIG_PROTECT='/usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/share/texmf/tex/generic/config/ /usr/share/
texmf/tex/platex/config/ /usr/share/config'
CONFIG_PROTECT_MASK=/etc/gconf
CVS_RSH=ssh
CXX=g++
DIRSTACK=()
DISPLAY=:0.0
EDITOR=/bin/nano
EUID=1000
GDK_USE_XFT=1
GROUPS=()
GS_LIB=/home/dadi/.kde/share/fonts
GTK_RC_FILES=/etc/gtk/gtkrc:/home/dadi/.gtkrc:/home/dadi/.gtkrc-kde
G_BROKEN_FILENAMES=1
HISTCONTROL=ignorespace
HISTFILE=/home/dadi/.bash_history
HISTFILESIZE=500
HISTSIZE=500
HOME=/home/dadi
HOSTNAME=kati
HOSTTYPE=i686
IFS=$' \t\n'
INFODIR=/usr/share/info:/usr/X11R6/info
INFOPATH=/usr/share/info:/usr/share/gcc-data/i686-pc-linux-gnu/3.2/info
INPUTRC=/etc/inputrc
JAVAC=/opt/blackdown-jdk-1.4.1/bin/javac
JAVA_HOME=/opt/blackdown-jdk-1.4.1
JDK_HOME=/opt/blackdown-jdk-1.4.1
KDEDIR=/usr/kde/3.1
KDEDIRS=/usr
KDE_MULTIHEAD=false
KONSOLE_DCOP='DCOPRef(konsole-5748,konsole)'
KONSOLE_DCOP_SESSION='DCOPRef(konsole-5748,session-2)'
LESS=-R
LESSOPEN='|lesspipe.sh %s'
LINES=39
LOGNAME=dadi
MACHTYPE=i686-pc-linux-gnu
MAIL=/var/mail/dadi
MAILCHECK=60
MANPATH=/usr/share/man:/usr/local/share/man:/usr/share/gcc-data/i686-pc-linux-gnu/3.2/man:/usr/X11R6/man:/opt/bla ckdown-jdk-1.4.1/man
MOZILLA_FIVE_HOME=/usr/lib/mozilla
OLDPWD=/home/dadi/mydir/dl/java/jakarta-tomcat-4.1.27/webapps/openreports/database
OPTERR=1
OPTIND=1
OSTYPE=linux-gnu
PAGER=/usr/bin/less
PATH=/usr/kde/3.1/bin:/bin:/usr/bin:/usr/local/bin:/opt/bin:/usr/i686-pc-linux-gnu/gcc-bin/3.2:/opt/Acrobat5:/usr /X11R6/bin:/opt/blackdown-jdk-1.4.1/bin:/opt/blackdown-jdk-1.4.1/jre/bin:/usr/qt/3/bin:/usr/kde/3.1/bin
PIPESTATUS=([0]="0")
PPID=5796
PROMPT_COMMAND='pwd>&8;kill -STOP $$'
PS1='\[\033[01;32m\]\u@\h \[\033[01;34m\]\W \$ \[\033[00m\]'
PS2='> '
PS4='+ '
PWD=/home/dadi/mydir/dl/java/jakarta-tomcat-4.1.27/webapps/openreports
QMAKESPEC=linux-g++
QTDIR=/usr/qt/3
SESSION_MANAGER=local/kati:/tmp/.ICE-unix/1694
SGML_CATALOG_FILES=/etc/sgml/sgml-ent.cat:/etc/sgml/sgml-docbook.cat:/etc/sgml/openjade-1.3.2.cat:/etc/sgml/sgml- docbook-3.0.cat:/etc/sgml/sgml-docbook-3.1.cat:/etc/sgml/sgml-docbook-4.1.cat:/etc/sgml/dsssl-docbook-stylesheets .cat:/etc/sgml/sgml-docbook-4.0.cat:/etc/sgml/sgml-lite.cat
SHELL=/bin/bash
SHELLOPTS=braceexpand:emacs:hashall:histexpand:history:interactive-comments:monitor
SHLVL=6
TERM=xterm
UID=1000
USER=dadi
XAUTHORITY=/home/dadi/.Xauthority
XINITRC=/etc/X11/xinit/xinitrc
_=mysqlcc

[meowsqueak]

I'm a complete n00b when it comes to MySQL and mysqlcc, but I came across this exact same problem today when I fired up mysqlcc for the first time ever. I quickly realised it would segmentation fault if I specified anything in the 'Name' field. If I leave it blank, it works fine.

[mobiusproject]

Just continuing an old thread because of the same problem without resolution. I emerged mysqlcc 0.93 today and everytime I run it I get a segmentation fault. It doesn't matter if I run it as root or as a normal user, as soon as I push a button (any button) or select anything from any of the drop down menus, the segmetation fault occurs. I have used this when working with Windows and would like to continue using it now that I am moving to Linux (yay!).

Thanks.

Mark

[caleb]

I would recommend trying 0.9.2 and seeing if it works for you.

[mobiusproject]

Thanks, .92 works just fine. Why is .93 unmasked if its still that buggy?

Moi

[RCMN]

same problem with x86-->mysqlcc-0.9.3

~x86 -->mysqlcc-0.9.4 works for me .....?

[mobiusproject]

If 0.9.4 works for you, use it. Thats what I am using now and am very happy with it.

[RCMN]

yes but it would be nice if 0.9.4 was in stable...

[meowsqueak]

There may be other bugs (known or unknown) that are keeping it in 'unstable'.

[arakune]

I'm experiencing the same problem with 0.9.3. Per a suggestion earlier in this thread, I was going to reinstall 0.9.2, however, when I looked in my portage directory I see that in a recent emerge sync all ebuilds for mysqlcc except for the masked 0.9.4 are no longer present. I'm going to try the 0.9.4 and see if that works any better, but I am curious what's happened to the older ebuilds. It seems odd to delete all of the stable versions while 0.9.4 is still masked......

[Carlo]

while 0.9.4 is still masked......

...and will be removed after while, since upstream development stopped. Read the ChangeLogs.

[arakune]

1) Changelog:

# ChangeLog for dev-db/mysqlcc
# Copyright 2002-2004 Gentoo Foundation; Distributed under the GPL v2
# $Header: /var/cvsroot/gentoo-x86/dev-db/mysqlcc/ChangeLog,v 1.21 2004/09/03 01:15:15 dholm Exp $

03 Sep 2004; David Holm <dholm@gentoo.org> :
Added to ~ppc.

*mysqlcc-0.9.4-r1 (20 Aug 2004)

20 Aug 2004; Carsten Lohrke <carlo@gentoo.org>
-files/mysqlcc-0.9.3-libmysqlclientac.patch,
+files/mysqlcc-0.9.4-shutdown.patch, -mysqlcc-0.9.3.ebuild,
+mysqlcc-0.9.4-r1.ebuild, -mysqlcc-0.9.4.ebuild:
stable on x86, will be package.masked shortly, #60745

29 Jun 2004; Aron Griffis <agriffis@gentoo.org> mysqlcc-0.9.3.ebuild,
mysqlcc-0.9.4.ebuild:
glibc -> libc

02 Jun 2004; Aron Griffis <agriffis@gentoo.org> mysqlcc-0.9.3.ebuild,
mysqlcc-0.9.4.ebuild:
Fix use invocation

09 May 2004; <SeJo@gentoo.org> mysqlcc-0.9.4.ebuild:
added ~ppc keyword

30 Mar 2004; Daniel Ahlberg <aliz@gentoo.org> mysqlcc-0.9.4.ebuild:
Adding amd64 keyword. Closing #43597.

*mysqlcc-0.9.4 (29 Dec 2003)

And so forth. I must be blind, because I see no reference to mysqlcc being completely removed from portage.

2) If it is being discontinued, why does that necessitate removing all ebuilds? Does gentoo require that all ebuilds in portage be currently supported? With the understanding of caveat emptor in place (which is always the case with such things), it seems a shame to remove wholesale a still useful and popular application from portage, even if it won't be developed further. Someone Else's Decision (possibly yours), of course, but I'm still saddened to see it go.

[Edited to fix formatting; content untouched]

[Carlo]

1) Changelog:

# ChangeLog for dev-db/mysqlcc
# Copyright 2002-2004 Gentoo Foundation; Distributed under the GPL v2
# $Header: /var/cvsroot/gentoo-x86/dev-db/mysqlcc/ChangeLog,v 1.21 2004/09/03 01:15:15 dholm Exp $

03 Sep 2004; David Holm <dholm@gentoo.org> :
Added to ~ppc.

*mysqlcc-0.9.4-r1 (20 Aug 2004)

20 Aug 2004; Carsten Lohrke <carlo@gentoo.org>
-files/mysqlcc-0.9.3-libmysqlclientac.patch,
+files/mysqlcc-0.9.4-shutdown.patch, -mysqlcc-0.9.3.ebuild,
+mysqlcc-0.9.4-r1.ebuild, -mysqlcc-0.9.4.ebuild:
stable on x86, will be package.masked shortly, #60745

2) If it is being discontinued, why does that necessitate removing all ebuilds?

Known bugs. It is not removed yet, btw. - but it will.

Does gentoo require that all ebuilds in portage be currently supported?

It depends. If an application is bug free, then there is no need to remove it.

it seems a shame to remove wholesale a still useful and popular application from portage, even if it won't be developed further.

You can unmask it, if it makes sense for you. Even after removal of ebuilds, you can grab them via webcvs and put them in your local overlay.

[garion911]

Anyone know of any similar prg in portage that can be used in place of it?

Right now, it works for me (except for a crash when adding a field to a table)...

--Garion

[LinuxRocks]

Just go here
http://www.mysql.com/products/mysqlcc/

and download the binary from them. Works like a charm and no need to install mysql database.

Joe