Version: 1.1.0 (using KDE KDE 3.4.3) Installed from: Gentoo Packages Kst is very unstable in my system. I open kst. I try to add a new vector. and kst crashes The backtrace I get: (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) .... (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912576148912 (LWP 2272)] [New Thread 1082132832 (LWP 2336)] 0x00002aaaaec21eba in waitpid () from /lib/libpthread.so.0 #0 0x00002aaaaec21eba in waitpid () from /lib/libpthread.so.0 #1 0x00002aaaac6c9fc1 in KCrash::defaultCrashHandler () from /usr/kde/3.4/lib64/libkdecore.so.4 #2 0x00002aaaaf502890 in killpg () from /lib/libc.so.6 #3 0x0000000000000000 in ?? () #4 0x0000000000000000 in ?? () #5 0x0000000000000000 in ?? () #6 0x00002aaa00000002 in ?? () #7 0x0000000000000000 in ?? () #8 0xfefefefefefefeff in ?? () #9 0x00000000000008e0 in ?? () #10 0x0000000000000001 in ?? () #11 0x00002aaaad57af70 in QRealMutexPrivate::lock () from /usr/qt/3/lib64/libqt-mt.so.3 #12 0x0000000000000000 in ?? () #13 0x00000000006d5db0 in ?? () #14 0x00000000009e02c8 in ?? () #15 0x00007fffff999fc0 in ?? () #16 0x0000000000000000 in ?? () #17 0x00007fffff999df0 in ?? () #18 0x0000000000000000 in ?? () #19 0x0000000000000001 in ?? () #20 0x000000000000000c in ?? () #21 0x00000000009ca5d0 in ?? () #22 0x000000000000000c in ?? () #23 0x00007fffff999d40 in ?? () #24 0x00002aaaab4369ad in KST::Plugin::symbol () from /usr/lib64/libkst.so.1 #25 0x00002aaaae4d4593 in dlerror () from /lib/libdl.so.2 #26 0x00002aaaae4d41e9 in dlsym () from /lib/libdl.so.2 #27 0x00002aaaac77ed0c in lt_dladderror () from /usr/kde/3.4/lib64/libkdecore.so.4 #28 0x0000000000000000 in ?? () #29 0x0000000000000000 in ?? () #30 0x0000ffff00001fa0 in ?? () .... #91 0x00000000007f20e0 in ?? () #92 0x00002aaaaf0fff1e in operator delete () from /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/libstdc++.so.6 #93 0x00002aaaab433e2b in KstDataSource::cleanupForExit () from /usr/lib64/libkst.so.1 #94 0x00002aaaab434fe0 in KstDataSource::supportsTime () from /usr/lib64/libkst.so.1 #95 0x00002aaaaad2c577 in KstVectorDialogI::updateCompletion () from /usr/lib64/libkstapp.so.1 #96 0x00002aaaaad300c7 in KstVectorDialogI::qt_invoke () from /usr/lib64/libkstapp.so.1 #97 0x00002aaaad325f08 in QObject::activate_signal () from /usr/qt/3/lib64/libqt-mt.so.3 #98 0x00002aaaad3261c0 in QObject::activate_signal () from /usr/qt/3/lib64/libqt-mt.so.3 #99 0x00002aaaabc6eeb5 in KURLRequester::textChanged () from /usr/kde/3.4/lib64/libkio.so.4 #100 0x00002aaaabc6f593 in KURLRequester::qt_emit () from /usr/kde/3.4/lib64/libkio.so.4 #101 0x00002aaaad325f7a in QObject::activate_signal () from /usr/qt/3/lib64/libqt-mt.so.3 #102 0x00002aaaad3261c0 in QObject::activate_signal () from /usr/qt/3/lib64/libqt-mt.so.3 #103 0x00002aaaad615785 in QLineEdit::textChanged () from /usr/qt/3/lib64/libqt-mt.so.3 #104 0x00002aaaad3df19c in QLineEditPrivate::finishChange () from /usr/qt/3/lib64/libqt-mt.so.3 #105 0x00002aaaabc6e3c2 in KURLRequester::setURL () from /usr/kde/3.4/lib64/libkio.so.4 #106 0x00002aaaaad2d13a in KstVectorDialogI::_fillFieldsForNew () from /usr/lib64/libkstapp.so.1 #107 0x00002aaaaad2d1ee in KstVectorDialogI::show_New () from /usr/lib64/libkstapp.so.1 #108 0x00002aaaaad3004d in KstVectorDialogI::qt_invoke () from /usr/lib64/libkstapp.so.1 #109 0x00002aaaad325f08 in QObject::activate_signal () from /usr/qt/3/lib64/libqt-mt.so.3 #110 0x00002aaaad326672 in QObject::activate_signal () from /usr/qt/3/lib64/libqt-mt.so.3 #111 0x00002aaaac0378f3 in KAction::slotPopupActivated () from /usr/kde/3.4/lib64/libkdeui.so.4 #112 0x00002aaaac037aeb in KAction::qt_invoke () from /usr/kde/3.4/lib64/libkdeui.so.4 #113 0x00002aaaad325f08 in QObject::activate_signal () from /usr/qt/3/lib64/libqt-mt.so.3 #114 0x00002aaaad608cb6 in QSignal::signal () from /usr/qt/3/lib64/libqt-mt.so.3 #115 0x00002aaaad33c83d in QSignal::activate () from /usr/qt/3/lib64/libqt-mt.so.3 #116 0x00002aaaad413ab1 in QPopupMenu::mouseReleaseEvent () from /usr/qt/3/lib64/libqt-mt.so.3 #117 0x00002aaaad358119 in QWidget::event () from /usr/qt/3/lib64/libqt-mt.so.3 #118 0x00002aaaad2cd37d in QApplication::internalNotify () from /usr/qt/3/lib64/libqt-mt.so.3 #119 0x00002aaaad2cd8ae in QApplication::notify () from /usr/qt/3/lib64/libqt-mt.so.3 #120 0x00002aaaac63fb91 in KApplication::notify () from /usr/kde/3.4/lib64/libkdecore.so.4 #121 0x00002aaaad273041 in QETWidget::translateMouseEvent () from /usr/qt/3/lib64/libqt-mt.so.3 #122 0x00002aaaad271d18 in QApplication::x11ProcessEvent () from /usr/qt/3/lib64/libqt-mt.so.3 #123 0x00002aaaad282f4b in QEventLoop::processEvents () from /usr/qt/3/lib64/libqt-mt.so.3 #124 0x00002aaaad2e14f5 in QEventLoop::enterLoop () from /usr/qt/3/lib64/libqt-mt.so.3 #125 0x00002aaaad2e1452 in QEventLoop::exec () from /usr/qt/3/lib64/libqt-mt.so.3 #126 0x000000000040aed4 in ?? () #127 0x00002aaaaf4f0674 in __libc_start_main () from /lib/libc.so.6 #128 0x000000000040573a in ?? () #129 0x00007fffff99bab8 in ?? () ... #1322 0x0000000000000000 in ?? ()
Maybe it is related to amd64 . I have linux gentoo amd64 native. kde 3.4.3
On Tuesday 08 November 2005 04:44, manolis wrote: > 2005-11-08 10:44 ------- Maybe it is related to amd64 . > I have linux gentoo amd64 native. kde 3.4.3 It looks like it happens when you use plugins/fits/filters. Does it happen when you don't use those?
Just out of curiosity, are you using Qt 3.3.4 or 3.3.5? Kst currently spews lots of X errors and becomes unuseable on Debian sid (Qt-3.3.5/KDE-3.4.3), but works perfectly on Ubuntu Breezy (Qt-3.3.4/KDE-3.4.2). This is probably unrelated, but it would be interesting to know, just to have another data point... -Ted On 8 Nov 2005 09:43:14 -0000, manolis <manolis@koppermind.homelinux.org> wrote: [bugs.kde.org quoted mail]
Regarding comment #2: If you mean the filters from Settings->Filters yes. There are about 12 "Fit *" filters. But I did not install them manually. They installed by my distribution (gentoo) when I select to install kst. I removed them from the list and the crash When I select Data->New Vector from a clean kst , still happens.
Regarding comment #3: No, I use Qt 3.3.4 . Gentoo doesn let me install qt 3.3.5 because it is broken with kde 3.4.3
> Regarding comment #3: > No, I use Qt 3.3.4 . Gentoo doesn let me install qt 3.3.5 because it is broken with kde 3.4.3 Ok, thanks for the additional info. The bulk of Debian/KDE 3.4.3 (everything I've tested) works fine with Qt 3.3.5- just not kst. Oh well... -Ted
On Tuesday 08 November 2005 11:13, manolis wrote: > If you mean the filters from Settings->Filters yes. There are about 12 "Fit > *" filters. But I did not install them manually. They installed by my > distribution (gentoo) when I select to install kst. I removed them from the > list and the crash When I select Data->New Vector from a clean kst , still > happens. Can you send me a .kst file along with data file that always reproduces this crash? Or even better, attach it to the bug report. I want to see if it crashes for me. It is known that plugins can crash or misbehave on 64bit machines but you seem to have found something else. This particularly interests me now: #94 0x00002aaaab434fe0 in KstDataSource::supportsTime () from /usr/lib64/libkst.so.1 Thanks
I am developing on a amd64 running gentoo.... but I haven't tried the emerged version on it. I am on travel right now, but when I return, I will look into it. As George mentioned, a .kst file which reproduces it would be great. I would also like to know what your compile options are set to in gentoo.
Regarding comment #7: Sorry but I am not familiar with kst. I just found out on the net for it and I emerged it to test it. The thing is that I don't need to make a kst file for crash. I just open the kst , I select data->Add vector. And the crash happens all the time. There is no open file. Regarding comment #8: I use a typical cflags rule set. CFLAGS="-march=k8 -O2 -pipe", not anything peculiar about it. It would be great If you could test the "emerge kst" version
On Tuesday 08 November 2005 15:43, manolis wrote: > 2005-11-08 21:43 ------- Regarding comment #7: > Sorry but I am not familiar with kst. I just found out on the net for it > and I emerged it to test it. The thing is that I don't need to make a kst > file for crash. I just open the kst , I select data->Add vector. And the > crash happens all the time. There is no open file. Then there is something very wrong with either the code you have or the build you are getting. We all use Kst without these problems of course. You might want to try a -O0 -g i386 build to compare.
I just verified that gentoo kst on x86 does not exibit this behavior.
I just emerged the kst 1.1.1 version that came up in ~amd64. The problem disappeared!!!