DebuggerConfigWidgetBase debugger_config_widget 0 0 558 627 Debugger Configuration unnamed textLabel1 Debug arguments can be set on the Run Options page or directly in the project manager gdbPath_label 4 5 0 0 Debugger executable: gdbPath_edit gdbPath_edit Gdb executable To run "gdb" binary from $PATH, leave this field empty. To run custom gdb, for example, for a different architecture, enter the executable name here. You can either run gdb from $PATH, but with a different name (say, "arm-gdb"), by typing the name here, or specify full path to the gdb executable. debuggingShell_label 4 5 0 0 Debugging &shell: debuggingShell_edit Run gdb in a special shell (mainly for automake projects) If you want gdb to be executed by a special shell or tool insert it here. The main use-case is for Automake based projects where the application is actually only a script and libtool is needed to get it to run inside gdb. debuggingShell_edit Run gdb in a special shell (mainly for automake projects) If you want gdb to be executed by a special shell or tool insert it here. The main use-case is for Automake based projects where the application is actually only a script and <b>libtool</b> is needed to get it to run inside gdb. layout4 unnamed groupBox2 Options unnamed asmDemangle_box Display &demangled names When displaying the disassembled code you can select to see the methods' mangled names. However, non-mangled names are easier to read. breakOnLoadingLibrary_box Try settings &breakpoints on library loading If GDB has not seen a library that will be loaded via "dlopen" then it will refuse to set a breakpoint in that code. We can get GDB to stop on a library load and hence try to set the pending breakpoints. See the documentation for more details relating to this behavior. If you are not "dlopen"ing libs then leave this unchecked. dbgTerminal_box Enable separate terminal for application &IO This allows you to enter terminal input when your application contains terminal input code (e.g. cin, fgets, etc.). If you use terminal input in your application then check this option. Otherwise leave it unchecked. enableFloatingToolBar_box E&nable floating toolbar Use the floating toolbar. This toolbar always stays on top of all windows so that if the app covers TDevelop you have control of the app through the small toolbar. It can also be docked into the panel. This toolbar is in addition to the toolbar in TDevelop. displayStaticMembers_box Display static &members Displaying static members makes GDB slower in producing data within TDE and TQt. It may change the "signature" of the data which TQString and friends rely on, but if you need to debug into these values then check this option. layout3 unnamed globalOutputRadix Global Output Radix unnamed outputRadixOctal Oct&al outputRadixHexadecimal He&xadecimal outputRadixDecimal Decimal buttonGroup2 Start Debugger With unnamed radioFramestack Framestack radioGDB GDB Output groupBox1 Remote Debugging This script is intended for the actual commands needed to connect to a remotely running executable. shell sleep 5 wait for remote program to start target remote ... connect to the remote debugger continue [optional] run debugging to the first breakpoint. unnamed layout1 unnamed runShellScript_label R&un shell script: Shell script to be executed at run time runShellScript_edit runGdbScript_edit Script to connect with remote application This script is sourced by gdb after the two preceding scripts have been executed. This script is intended for the actual commands needed to connect to a remotely running executable. shell sleep 5 wait for remote program to start target remote ... connect to the remote debugger continue [optional] run debugging to the first breakpoint. runShellScript_edit Script to start remote application This shell script is run after the Config gdb script has been sourced by gdb. When debugging remotely this script is intended to actually start the remote process. [It is expected that the debug executable can be reached on the target, maybe by downloading it as a final build step] 1) Find a way to execute a command remotely - rsh, ssh, telnet, ... 2a) Execute "gdbserver ... application" on target. or if your executable contains the gdb stub 2b) Execute "application" on target. runGdbScript_label Run &gdb script: Gdb script to be executed at run time. runGdbScript_edit configGdbScript_label &Config gdb script: configGdbScript_edit configGdbScript_edit Gdb configure script This script is sourced by gdb when the debugging starts. spacer1 Vertical Expanding 20 16 debuggingShell_edit gdbPath_edit displayStaticMembers_box asmDemangle_box breakOnLoadingLibrary_box enableFloatingToolBar_box dbgTerminal_box outputRadixOctal outputRadixDecimal outputRadixHexadecimal configGdbScript_edit runShellScript_edit runGdbScript_edit kdialog.h kurlrequester.h