Hello dear lazyweb,
I have a problem that I could not solve nor find help by my usual paths. I’m speaking about a deadlock on shutdown I get sometimes with what will become KDevelop 4.1. You can find a backtrace in this bug report:
The thing is this: Apparently some global
QMutex is getting destroyed by the exit handler but the call to
__pthread_cond_destroy does not return.
I have no clue on how to fix this. Is there at least a way to find out which mutex this is? Someone told me to have a look in
/proc/PID/maps but there I only found out that - what a suprise -
~QMutex is defined in
libQtCore.so… Or should I have looked for the
this=0xfffffe00 address? Speaking of which - isn’t that address messed up?
Does anyone have a better idea?
Hey there :)
As I announced on the kde-core-devel mailing list, I planned to improve Dr Konqi for a long time, as for me as a developer it is an invaluable tool. Well, yesterday I sat down and implemented the first two things which I wanted for a long time:
Once the backtrace got loaded, Dr Konqi will automatically scroll to the line that contains
[KCrash Handler]. No need to find that manually anymore. Awesome :)
Yeah, you should know that I as a KDevelop user and developer am addicted to syntax highlighting. That’s what I did for Dr Konqi as well now:
Dr Konqi with syntax highlighted GDB backtrace
So anyone using KDEBase trunk will now have a shiny Dr Konqi :) Feedback appreciated, esp. whether more or less should be highlighted. I personally found it overly colorful when I also highlighted pointer adresses (ignore the bug in that outdated screenshot). What do you think?