Le Sat, 30 Apr 2011 15:10:48 -0700 (PDT), Darrell Anderson <humanreadable@...> a �crit : > What is the best way to troubleshoot run-time crashes? > > Do the packages have to be built a certain way? You have to build kdepim (no need, at least for now, to recompile other packages) including "-g" in your CFLAGS and CXXFLAGS in order to have a useful backtrace. > > I've read about backtraces, core dumps, and using gdb. I'm no > programmer, so what is the best way for me to troublesoot? $ gdb (gdb) file /usr/bin/kmail (gdb) run <trigger the crash> (gdb) bt <you obtain the backtrace> I don't know if this will be enough, but I'm not an expert debugger :). > > In particular, I am running KDE 3.5.10, recompiled for Slackware > 13.1. KMail always now crashes whenever I try to do anything with the > composer window (save as draft, send, etc.). Boom. Just disappears. > Almost as if I had started KMail with the --compose option. The app > disappears and I have to restart KMail. The funny thing is the > message gets stored in the Outbox. > > I want to troubleshoot in case this bug carries over to Trinity. > > Thanks. > > Darrell > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > trinity-devel-unsubscribe@... For additional > commands, e-mail: trinity-devel-help@... Read > list messsages on the Web archive: > http://trinity-devel.pearsoncomputing.net/ Please remember not to > top-post: > http://trinity.pearsoncomputing.net/mailing_lists/#top-posting >