Summary: | my own backtraces collection(7) | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Ilya Platonov <ill> |
Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | 1.2.4 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Ilya Platonov
2005-05-30 06:17:44 UTC
Well, no. Take a look at the backtraces, it's crashing inside of kdelibs, mostly with KConfig operations: #3 0x40d63553 in KConfig::lookupData () from /usr/lib/libkdecore.so.4 Something's broken with your kdelibs, I'd say. I'm just using standard kdelibs 3.3.2-6 from Debian sarge. I'm just using standard kdelibs 3.3.2-6 from Debian sarge. Yes, seems to be related to problems with kdelibs. From your first backtrace, for example, how would this code break something: QImage nocover( locate( "data", "amarok/images/nocover.png" ) ); Backtraces #1, #4 , #5 and #6 claim to be triggered by this same code, though it's crashing in different ways (always inside of kdelibs). 7 is triggered by a similar function, that really seems to be ok (as far as amaroK is concerned). #2 crashed in Kconfig, and #3 is a crash in sizeHint() function. Man, with kdelibs behaving like this I'm surprised amaroK even starts. Really, all too bizarre. Check your kdelibs(-devel), something must be broken. try other version or something. At least, try to compile some other kde application from source and tell us if this will be crashy like this too. I had amarok 1.2.3 installed from Debian distro before, and there was a lot of crashes. Other KDE applications works fine. May be it is a matter of not really correct multi-threading programming :). You know, you can have a lot of hidden problems with this stuff. For example, I had crashes when some Thread tryed to autoscan my music for new files, I have just turned off this feature. Still I'll try to do something with my libs. *** Bug 106374 has been marked as a duplicate of this bug. *** Do you use p4 with hyper threading on? Yes I do. |