Crash-on-exit: The gist of it all, and finally the solution :)

Mark Kretschmann kretschmann at kde.org
Mon Mar 2 13:22:44 CET 2009


Hey Amarokers,

as some of you have noticed, I've spent the last few days with chasing
down an obscure crash on exit in Amarok trunk. Today, after discussing
with David Faure, we could finally unravel the mystery:

The bad:
  It's a bug in KDElibs 4.2.0.

The good:
  It's fixed in KDE trunk, and backported to 4.2.1, which is tagged
and soon to be released :)


Here's the Amarok bug report for it, including countless commits I
made while chasing the bug (some of which could be reverted, others
might still be useful):

  https://bugs.kde.org/show_bug.cgi?id=185789

Here are the fixing commits in KDE trunk, and in the 4.2 branch:

  http://websvn.kde.org/?view=rev&revision=918168
  http://websvn.kde.org/?view=rev&revision=918169

What I learned from the whole thing:

  1) From now on run KDElibs with debugging symbols 2) Shit happens 3)
Sometimes shit happens ;)

Additionally, you can here find a valgrind memcheck analysis from
latest Amarok trunk:

  http://mark.kollide.net/valgrind_amarok_2_mar_2009.txt


David Faure showed me some tricks for getting better valgrind logs,
including suppressing some false positives:

valgrind --log-file=$HOME/valgrind_amarok_2_mar_2009.txt
--num-callers=50 --suppressions=/home/mark/Documents/kde.supp amarok
-m --nofork

  (kde.supp can be downloaded here:
http://websvn.kde.org/*checkout*/trunk/KDE/kdesdk/scripts/kde.supp?revision=901161)


I would like to say a big Thank You to David Faure for helping us. You
rock, David :)

-- 
Mark Kretschmann
Amarok Developer
www.kde.org - amarok.kde.org


More information about the Amarok-devel mailing list