Version: (using Devel) OS: Linux Installed from: Compiled sources You should add some backtrace parsing to see if the generated backtrace is actually useful. If not useful don't show it to the user and add a message have to produce a valid one.
Created attachment 30152 [details] Search backtrace for "no debugging symbols found" and if it's present tell user that it's not useful My initial proposal to fix it. Maybe it's better to show the message along with the potentially useless backtrace.
Declaring a backtrace is unuseful just for a single "no debugging symbols found" is plain wrong. You could have the application using a 3rd party library w/o debug symbols and appearing in the backtrace, but yet the backtrace being useful (ie having symbols for the useful part of it).
Than what, better parsing or mission impossible (close it)? I opened this because every time I saw someone reported "no debugging symbols" backtrace, devs said it's useless.
I'm implementing it in my new DrKonqi proposal ( currently at: http://websvn.kde.org/branches/work/drkonqi-newdialog/ )
The new DrKonqi implementation was moved to KDE4.3trunk. It handles the missing debug symbols better and it also properly analyzes the backtrace to determine its quality.