if checked, CodeLite will display the value of e.g.
Limit how many elements GDB will print - for very large arrays, the resulting display wouldn't fit on the screen. Last is two items related to how things are displayed: If you check this box, the output appears in both places. In previous CodeLite versions it used to appear as a tooltip. While debugging, show debugger tooltips - the output from hovering over a variable now appears in the the Ascii Viewer. Use file name only for breakpoints (NO full paths) - useful for remote debugging. Unchecking this box theoretically prevents the window appearing in practice, it still does anyway :( Show debugger terminal - when debugging starts, a terminal window appears program output may appear there. This is mostly useful if you're trying to debug CodeLite's debugging. Enable full debugger logging - if checked, CodeLite will emit a large number of messages in the Debug tab. 
Break at assertion failure (MinGW only) - This is necessary on MinGW without it, the application being debugged will crash if it asserts, preventing you from debugging the cause. If so, set a breakpoint on main, then do 'catch throw'. this will fail for some versions of gdb, on some platforms. Break when C++ exception is thrown - makes gdb break when an exception is thrown. This is useful when setting breakpoints inside a shared libraries / DLLs Apply breakpoints after main function is hit - this option tells the debugger to set a temporary break point at main and once this breakpoint is reached, it should set the user breakpoints. Breaking at main() gives you the opportunity to set them before your app crashes ) Automatically set breakpoint at main - this can be useful if gdb can't find your breakpoints' source files until the app is running. Enable pending breakpoint - this is self-explanatory it may or may not work, depending on your platform and gdb version. The next field is a collection of breakpoint options: If you wish to change a debugger per-project, you can do so from the 'Project Settings' dialog, under the 'Debugger' page. Note that this is a global setting and it will affect all the projects. 
However, if your installed gdb can't be found, or if you have more than one version available, you can specify the filepath here. The first field is the Path to the debugger, and will usually be blank.
0 kommentar(er)
