Version: 4.2.2-0ubuntu1 (using KDE 4.2.2) OS: Linux Installed from: Ubuntu Packages I wish to change item (1) to item (2) in kdebase/drkonqi/backtrace.cpp: (1) ::write(handle, "bt\n", 3); // this is the command for a backtrace (1) ::write(handle, "bt full\n", 8); // this is the command for a backtrace
In DrKonqi2 (KDE4.3) you can customize the commands GDB will use in a simple way: - Open with an editor the file: "$KDEDIR/share/apps/drkonqi/debuggers/gdbrc" ($KDEDIR is the path where KDE is installed) - Modify the last line of the file to set the custom commands. The default line is: "BacktraceCommand=set width 200\nthread\nthread apply all bt" If you modify it to : "BacktraceCommand=set width 200\nthread\nthread apply all bt full" you will get the full backtrace. Thanks
Well, there are some issues to solve/consider prior to this "bt full" change, if it is ever going to happen. 1. DrKonqi now uses GdbHightligheter class to highlight backtrace obtained from gdb, and that means switching to "bt full" makes drkonqi itself crash for me when showing the backtrace. 2. using "bt full" will significantly increase the size of the backtrace and thus the report, which makes bug 248807 more likely to be triggered. 3. For searching duplicate, I don't think using "bt full" is a good news. In general, I'm skeptical of the benefit of using "bt full" as default. Maybe drkonqi can ask gdb to generate two backtraces, and send the "bt full" one as one additional attachment.
I'm with Jekyll on this one. What's more, bt full will not necessarily yield all that much information on release builds because the compiler will optimize a lot of stuff out anyway. And of the stuff that remains there's a reaallly good chance it will leak passwords by accident.