Created attachment 49571 [details] drconqui raload of backtrace Version: unspecified (using KDE 4.4.3) OS: Linux I updated my Mandriva 2010.0 to 2010.1 and got Amarok crash (https://bugs.kde.org/show_bug.cgi?id=245990). When I install qt4-debug package drkonqui fails to load the backtrace. Version of drconqui is 2.1.0 Reproducible: Didn't try
This is probably because something killed amarok in the background or gdb crashed or something like that. Although unlikely, these things can happen... Now if I could understand the messages in the screenshot, I could probably tell you more precisely what might have happened. I don't consider this to be a drkonqi bug, as there is nothing drkonqi can do in such cases other than display an error message.
Created attachment 50853 [details] Beginning of backtrace generation
Created attachment 50854 [details] Continuing of backtrace generation
Created attachment 50855 [details] End of backtrace generation
Created attachment 50856 [details] Error
So this is reproducable?? Well, as I thought... gdb crashes. This is a gdb bug. However, I see that it generates most of the backtrace, so perhaps it should at least display whatever it has managed to collect from the output. I will fix that.
This is getting fairly meta. We've talked about this a bit and think that there is little use to this. Gdb these days crashes just about never, and when it does drkonqi surely isn't the tool to use for debugging that.
As "http://bugs.kde.org/show_bug.cgi?id=454411" demonstrates, for me, DrKonqi reproducibly crashes when I install gdb whilst DrKonqi is operative. Diagnosis would be significantly less difficult if DrKonqi had provided the information that it would have if this proposition had been implemented. Consequently, please reconsider this.