/lib/libthread_db.so.1 crashes at shutdown or reboot on Slackware 10.1 with Qt 3.3.4
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
/lib/libthread_db.so.1 crashes at shutdown or reboot on Slackware 10.1 with Qt 3.3.4
Hi,
I get the error message below most of the time when I restart or shutdown my pc.
I am currently running Slackware 10.1 with Qt 3.3.4 and KDE 3.4.1 both compiled from source.
I got the message on kernel 2.4.29 as well as kernel 2.6.11.11
Do you think that I did something wrong during Qt compilation?
Code:
Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 5225)]
[KCrash handler]
#5 0xb7460cd1 in QGList::find ()
from /usr/local/qt-x11-free-3.3.4/lib/libqt-mt.so.3
#6 0xb78419de in KGlobal::registerStaticDeleter ()
from /usr/local/kde/lib/libkdecore.so.4
#7 0xb7de4692 in KDirWatch::self () from /usr/local/kde/lib/libkio.so.4
#8 0xb7e3bb7a in KDirListerCache::KDirListerCache ()
from /usr/local/kde/lib/libkio.so.4
#9 0xb7e43709 in KDirListerCache::self () from /usr/local/kde/lib/libkio.so.4
#10 0xb7e4e22b in KDirLister::stop () from /usr/local/kde/lib/libkio.so.4
#11 0xb7e4d5b1 in KDirLister::~KDirLister ()
from /usr/local/kde/lib/libkio.so.4
#12 0xb6428e54 in SystemMenu::~SystemMenu ()
from /usr/local/kde/lib/kde3/kickermenu_systemmenu.so
#13 0xb7b8d4bf in QPtrList<QObject>::deleteItem ()
from /usr/local/kde/lib/libkdeui.so.4
#14 0xb7460c3c in QGList::clear ()
from /usr/local/qt-x11-free-3.3.4/lib/libqt-mt.so.3
#15 0xb784f1bb in KLibrary::~KLibrary ()
from /usr/local/kde/lib/libkdecore.so.4
#16 0xb7852192 in KLibLoader::close_pending ()
from /usr/local/kde/lib/libkdecore.so.4
#17 0xb7850d19 in KLibLoader::~KLibLoader ()
from /usr/local/kde/lib/libkdecore.so.4
#18 0xb784fc89 in KLibLoader::cleanUp ()
from /usr/local/kde/lib/libkdecore.so.4
#19 0xb7789db8 in KApplication::~KApplication ()
from /usr/local/kde/lib/libkdecore.so.4
#20 0xb7855bd3 in KUniqueApplication::~KUniqueApplication ()
from /usr/local/kde/lib/libkdecore.so.4
#21 0xb687b7c6 in Kicker::~Kicker ()
from /usr/local/kde/lib/libkdeinit_kicker.so
#22 0xb68798cf in kdemain () from /usr/local/kde/lib/libkdeinit_kicker.so
#23 0xb69127d0 in kdeinitmain () from /usr/local/kde/lib/kde3/kicker.so
#24 0x0804cd06 in launch ()
#25 0x0804e234 in handle_launcher_request ()
#26 0x0804e777 in handle_requests ()
#27 0x0804f7a8 in main ()
bunzip2 qt-x11-3.3.4.tar.bz2
tar xvf qt-x11-3.3.4.tar
cd qt-x11-3.3.4
less INSTALL
(Set up QTDIR, KDEDIR, PATH, LD_LIBRARY_PATH, XDG_DATA_DIRS and XDG_CONFIG_DIRS)
cd $QTDIR
./configure -system-zlib -qt-gif -system-libpng \
-system-libjpeg -plugin-imgfmt-mng -thread -no-stl \
-no-xinerama -no-g++-exceptions
make
Frankly, I don't know if it is related to your error
I first make a confusion between stl and tls (Thread-local storage support)
and tls was added in current glibc
But when I compared your options and the slackbuild configure options
for qt, I saw this major difference (there are other options in the
slackbuild script that you did not use too)
I think no as the kde programs use the qt shared libraries at runtime but
at compile, they use the qt header files (I don't think qt header files
changes if you enable or disable qt compile options)
I have tried the build script you suggested but the only themes I got were CDE, Motif, Platinum and maybe SGI.
Why does the script compiles Qt under /usr/lib and not /usr/local?
Will KDE work if I install Qt from Slackware 10.1 CD?
You compiled and installed 3.3.4 qt version , right ?
So I don't see a problem if you overwrite your qt install
with qt-3.3.4-i486-1 slackware packwage.
If you upgrade from current, consider upgrade glibc and gcc
[edit]
also coreutils and binutils
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.