Version: 1.3-beta2 (using KDE 3.4.1, Gentoo) Compiler: gcc version 3.4.4 (Gentoo 3.4.4, ssp-3.4.4-1.0, pie-8.7.8) OS: Linux (i686) release 2.6.11-gentoo-r10 This is weird, but on my system amaroK crashes if it is not compiled with -g. It crashes about two seconds after startup when reading my collection. I tried looking into many things, such as making sure that all libraries were built with the same compiler. I removed all the optimization options. Nothing seemed to help. So I added -g back onto the compiler options hoping to send a backtrace. Unfortunately I can't send a backtrace because building for debug mode makes the crash disappear. Here are some things of note: 1. The engine used doesn't matter, although I can't switch to the aRts engine (that's a separate issue). 2. The other compiler options don't matter. If -g is present, everything works fine. 3. It didn't matter how other libraries that amaroK uses are compiled. I tried every conceivable compilation on my libraries, all with the same result. 4. Running as root didn't make a difference, nor was it expected to. 5. It didn't matter whether I used KDE 3.4.1 or 3.4, but I didn't much expect it to. 6. Starting amarokapp directly simply makes the crash happen more quickly. 7. Deleting config files doesn't help. With no collection, amaroK won't crash when trying to read it, but it will as soon as a collection is created. If anyone can solve this, you will be immortalized at least in my mind as a hacker supreme.
I forgot to mention that this occurs with all versions of amaroK 1.2 and up.
Bizarre bug. Is the collection on a strange file system or something? Using MySQL workarounds the problem?
My collection resides in two separate directories on the same ReiserFS partition. I gave MySQL a try. At first I thought it fixed it, but instead the crash was merely delayed. Maybe because of the time spent logging into MySQL? Anyway, that makes me think that the problem could be with my collection, because the crash seems to come after it is scanned. But why only when debugging isn't built in?
what CFLAGS and CXXFLAGS are you using? Flags that will cause problems are -fomit-frame-pointer and -O3. We also need a backtrace. Please provide one if you can.
Please reopen if you feel this is still valid, and provide us with some more information, look here: http://amarok.kde.org/amarokwiki/index.php/Debugging_HowTo
Closing correctly as Amarok 1.x is unmaintained since quite some time anyway.