Summary: | quanta crashes during new project wizard | ||
---|---|---|---|
Product: | quanta | Reporter: | Jan Obrátil <jobratil> |
Component: | general | Assignee: | András Manţia <amantia> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | greg_g, juergen.haering, sigbjorn |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
crash backtrace
Crash backtrace |
Description
Jan Obrátil
2004-09-03 12:22:44 UTC
*** Bug 88797 has been marked as a duplicate of this bug. *** It was a bug in kdelibs, that I've just corrected. I cannot reproduce this anymore with the patched version. If you still see the problem after upgrading to KDE 3.3.2, please reopen the report. *** Bug 94511 has been marked as a duplicate of this bug. *** Hi, I have the same problem with quanta from KDE 3.3.2 installed from RedHat packages on Fedora Core 3. A crash only happens when a directory choosen for new project files is empty. Created attachment 8900 [details]
crash backtrace
I cannot reproduce it. :-( I don't know what is in the FC3 kdelibs 3.3.2 package, but either they didn't package the correct version or there is some other bug that I cannot see. Can you reproduce the crash in the way it was described in the original report? If yes, I say it's a problem of the binary package. If no, but you can reproduce in another way, let me know the steps you do, so I can try here as well. Well, of course I can reproduce it the same way as it is in original report. Moreover, any time I create a new project with wizzard and I choose an empty directory for project files, quanta crashes. If I start it again and while creating project with wizzard I choose non-empty dir (it may be the same dir when quanta crashed - it really doesn't matter), it will not crash. In this case all I can say is to try when 3.4 is released (or try 3.4Beta1 which will soon be released) as I cannot reproduce and I already committed a fix for this bug in kdelibs, which normally should be in 3.3.2. Isn't it possible to take some hints what could be wrong from the backtrace I have attached? I have also tried with binary package from kde-redhat.sourceforge.net but the problem also exists. I searched my archives, and it seems that my fix was for the same bug (as it can be reproduced), but the BT is different. > ------- Isn't it possible to take some hints what could be wrong from > the backtrace I have attached? I have also tried with binary package > from kde-redhat.sourceforge.net but the problem also exists. In order to have a real useful backtrace, you need to use a debug build of kdelibs. This means downloading from source and configure with --enable-debug=full. I'm trying to find similar reports to see if it is FC3 specific or not. Hm, it may be not, see http://bugs.kde.org/show_bug.cgi?id=94511. Andras Created attachment 11537 [details] Crash backtrace I've encountered the same bug in Quanta 3.4.1, with an almost identical backtrace, on Gentoo. Command line output: quanta Invalid entry (missing '=') at /usr/share/apps/quanta/doc/javascript.docrc:241 Quanta: Parsing time (0 lines): 0 ms Quanta: Parsing time (17 lines): 466 ms Quanta: Parsing time (10 lines): 0 ms Quanta: Parsing time (9 lines): 0 ms ASSERT: "holders" in kdirlister.cpp (427) KCrash: Application 'quanta' crashing... Some version / use flag information: sys-libs/glibc-2.3.4.20050125-r1 -build +debug -erandom -hardened (-multilib) +nls -nomalloccheck +nptl +nptlonly +pic -userlocales kde-base/quanta-3.4.1 -arts +debug +doc -kdeenablefinal -kdexdeltas +tidy -xinerama kde-base/kdelibs-3.4.1-r1 +alsa -arts +cups -debug +doc +jpeg2k -kdeenablefinal -kerberos -openexr -spell +ssl +tiff -xinerama -zeroconf cflags: CFLAGS="-O2 -march=pentium-m -pipe" I think https://bugs.kde.org/show_bug.cgi?id=99445 and http://bugs.kde.org/show_bug.cgi?id=95837 are duplicates of this bug. It'd be nice if this bug is reopened. |