On Sonntag, 6. Januar 2013 10:56:31 CEST, Myriam Schweingruber wrote: > Thank you for the debug output, but what we would need is a backtrace.
That will unlikely do. Since it's a malloc error (memory corruption) you'll have to run amarok in valgrind to get some reasonable idea about the source of the problem. gdb will get you to the memory corruption and (usually) print random backtraces (whatever happened when accessing the corrupted memory) Cheers, Thomas _______________________________________________ Amarok mailing list Amarok@kde.org https://mail.kde.org/mailman/listinfo/amarok
