From 17fa54ad22c1a475164c31c846f1fa5c0ca02972 Mon Sep 17 00:00:00 2001 From: Johannes Sixt Date: Sun, 24 Dec 2000 15:42:32 +0000 Subject: [PATCH] Updated the user's manual. --- kdbg/doc/en/Makefile.am | 19 +- kdbg/doc/en/argspwdenv.html | 44 +++++ kdbg/doc/en/breakptlist.html | 75 ++++++++ kdbg/doc/en/globaloptions.html | 69 +++++++ kdbg/doc/en/howdoi.html | 79 ++++++++ kdbg/doc/en/index.html | 425 +++++++++++++++++------------------------ kdbg/doc/en/localvars.html | 21 ++ kdbg/doc/en/memory.html | 27 +++ kdbg/doc/en/pgmoutput.html | 47 +++++ kdbg/doc/en/pgmsettings.html | 53 +++-- kdbg/doc/en/registers.html | 34 ++++ kdbg/doc/en/sourcecode.html | 31 +++ kdbg/doc/en/stack.html | 24 +++ kdbg/doc/en/threads.html | 41 ++++ kdbg/doc/en/tips.html | 45 +++++ kdbg/doc/en/types.html | 172 +++++++++-------- kdbg/doc/en/watches.html | 22 +++ 17 files changed, 877 insertions(+), 351 deletions(-) create mode 100644 kdbg/doc/en/argspwdenv.html create mode 100644 kdbg/doc/en/breakptlist.html create mode 100644 kdbg/doc/en/globaloptions.html create mode 100644 kdbg/doc/en/howdoi.html rewrite kdbg/doc/en/index.html (82%) create mode 100644 kdbg/doc/en/localvars.html create mode 100644 kdbg/doc/en/memory.html create mode 100644 kdbg/doc/en/pgmoutput.html create mode 100644 kdbg/doc/en/registers.html create mode 100644 kdbg/doc/en/sourcecode.html create mode 100644 kdbg/doc/en/stack.html create mode 100644 kdbg/doc/en/threads.html create mode 100644 kdbg/doc/en/tips.html create mode 100644 kdbg/doc/en/watches.html diff --git a/kdbg/doc/en/Makefile.am b/kdbg/doc/en/Makefile.am index c4dd3ec..d3edeb9 100644 --- a/kdbg/doc/en/Makefile.am +++ b/kdbg/doc/en/Makefile.am @@ -1,10 +1,25 @@ # add here all files -data_DATA = index.html types.html pgmsettings.html +data_DATA = \ + argspwdenv.html \ + breakptlist.html \ + globaloptions.html \ + howdoi.html \ + localvars.html \ + memory.html \ + pgmoutput.html \ + pgmsettings.html \ + registers.html \ + sourcecode.html \ + stack.html \ + threads.html \ + tips.html \ + types.html \ + watches.html \ + index.html # this is the directory, where all datas are installed # you have given the datas in data_DATA datadir = $(kde_htmldir)/en/kdbg EXTRA_DIST = $(data_DATA) - diff --git a/kdbg/doc/en/argspwdenv.html b/kdbg/doc/en/argspwdenv.html new file mode 100644 index 0000000..2cc8564 --- /dev/null +++ b/kdbg/doc/en/argspwdenv.html @@ -0,0 +1,44 @@ + + + + + + + KDbg - User's Manual - Arguments, Environment + + +Contents +

+Specifying program arguments, working directory, environment variables

+Choose Execution|Arguments to open a dialog where you can set program +arguments, the working directory for your program, and environment variables. +

+Program Arguments

+In the top edit box enter the arguments that shall be passed on to your +program. Next time the program is started, the new arguments will be used. +

+Working directory

+In the edit box below you can specify the working directory for your program. +Your program will use the new directory only when it is run the next time. +

The working directory also applies to gdb itself! The directory that +you specify will be passed to gdb immediately, i.e. gdb will work with +the new setting as soon as you press OK. This can influence whether +source code files are found. +

+Environment variables

+In the environment variables section type in an expression of the form +VARIABLE=value +to set the environment variable VARIABLE to the value value, +and click Modify. To remove a variable, select it from the list +below and click Remove. To change the value, edit the value in the +edit field and click Modify. If you change the name of the variable +and click Modify, you add a new variable! The new environment variables +will be used by your program the next time it is run. +

An important environment variable to set if you are using glibc2 on +Linux is LD_BIND_NOW. It is very important that you set this variable +to 1 for all your debugging sessions. If it is not set, gdb cannot +step into and out of system functions that are imported from the shared +libc +and other libraries. + + diff --git a/kdbg/doc/en/breakptlist.html b/kdbg/doc/en/breakptlist.html new file mode 100644 index 0000000..e881b2a --- /dev/null +++ b/kdbg/doc/en/breakptlist.html @@ -0,0 +1,75 @@ + + + + + + + KDbg - User's Manual - Breakpoint list + + +Contents +

+The Breakpoint List

+The breakpoint list displays all breakpoints and watchpoints that are set +and allows you to manipulate them. It can be displayed using View|Breakpoints. +

+The list of breakpoints

+For each breakpoint the following is shown: + +The icon in front of the entry indicates whether the breakpoint is enabled +(a red dot) or disabled (a bright red dot), whether the breakpoint is temporary +(a tiny clock is overlaid) or whether the breakpoint is conditional (a +tiny question mark is overlaid). +

Watchpoints are indicated by an eye glas icon in front of the line. +

+Manipulating breakpoints

+It is important to note that breakpoints and watchpoints +cannot be manipulated while the program is running. If the program has +already been started, it must stop first - either by hitting a breakpoint +that is already set or forcefully by choosing Execution|Break. Note +that this will not terminate the program, it just interrupts it. You can +now manipulate the breakpoints; then choose Execution|Continue to +let the program continue. +

To set a breakpoint on a specific source line, it is easiest to do this +in the source code window. If you don't know the exact file and line number +of a function, you can set the breakpoint by typing the function name in +the edit box above the list and click Add Breakpoint. +

You can disable and enable breakpoints by selecting them in the list +and clicking Disable or Enable. Or you simply click on the +breakpoint in the list using the middle mouse button - just like you enable +and disable breakpoints in the source window. +

You can set a condition on a breakpoint (so that the program is only +stopped if the condition is true) or set an ignore count (so that the program +is not stopped the next n times that the breakpoint is hit). To do that, +press the Conditional button and enter the condition and/or ignore +count. +

+Manipulating watchpoints

+Watchpoints are a like breakpoints, except that they interrupt the program +when the value of a memory location changes. As with breakpoints, watchpoints +cannot be manipulated while the program is running. See above +for more information. +

To set a watchpoint, type an expression in the edit box above the list, +then click Add Watchpoint. The program will stop when the value +of the expression changes. Note that watchpoints that involve local variables +can only be set when the program is stopped in a breakpoint (or has been +interrupted by Execution|Break). +

To remove the watchpoint, select it from the list and click Remove. +If the expression involves a local variable, the watchpoint will be removed +automatically when the program leaves the current frame. +

You can set a condition and an ignore count on the watchpoint just like +on breakpoints by selecting it and clicking Conditional. + + diff --git a/kdbg/doc/en/globaloptions.html b/kdbg/doc/en/globaloptions.html new file mode 100644 index 0000000..98889d6 --- /dev/null +++ b/kdbg/doc/en/globaloptions.html @@ -0,0 +1,69 @@ + + + + + + + KDbg - User's Manual - Global Options + + +Contents +

+Global Options Dialog

+To specify some global options, choose File|Global Options. You +can set the following: + + +

+How to invoke gdb

+ +
If you want to use a different version of gdb, you can specify +it under +How to invoke GDB. The default command is gdb --fullname +--nx. Be sure to also specify these options if you change the gdb +executable. If you leave them away, KDbg will not work. If you messed up +the entry, you can clear it to revert to the default setting.
+ +

+How to invoke a terminal emulator

+ +
If you want to use a different terminal program to show the +output of the program, specify it under Terminal for program output. +The default setting is xterm -name kdbgio -title %T -e sh -c %C. +In this entry, +%T will be replaced by a title string, %C +will be replaced by a Bourne shell script that loops infinitely so that +the terminal window doesn't close. (No, it doesn't use CPU, it calls sleep +3600 in a loop :) An alternative for this setting could be konsole +-nowelcome -name kdbgio -caption %T -e sh -c %C.
+ +

+Pop into foreground

+ +
You can specify whether the KDbg window shall move itself into +the foreground as soon as the program being debugged stops (at a breakpoint +or due to a signal). The KDbg window is not activated, however (at least +under KWM, the KDE window manager). Some users may feel that this behavior +is intrusive, so this option is off by default.
+ +
If this option is on, KDbg will also retreat itself into the +background when the program is continued by any command, but it does so +only after a timeout that can be specified. This avoids that the debugger +window flashes back and forth each time you click any of the Step +commands.
+ + + diff --git a/kdbg/doc/en/howdoi.html b/kdbg/doc/en/howdoi.html new file mode 100644 index 0000000..7bf64f0 --- /dev/null +++ b/kdbg/doc/en/howdoi.html @@ -0,0 +1,79 @@ + + + + + + + KDbg - User's Manual - How Do I...? + + +Contents +

+How Do I...?

+ +

+... set breakpoints?

+There's more than one way to set a breakpoint: + +If you can't set breakpoints, maybe the program is currently running. You +can't set breakpoints while the program is running. Stop it first using +Execution|Break. +If you still can't set breakpoints, make sure that you have compiled and +linked your program with debugging information enabled. +

+... display the value of a global variable or an arbitrary expression?

+Use the Watch window. +

+... set watchpoints?

+Watchpoints are manipulated in the breakpoint +list. +

+... use a core dump?

+First load the executable using File|Executable, then specify the +core dump using File|Core dump. +

+... debug a program that's caught in an endless loop?

+Start the program and let it run until it is in the endless loop. Then +switch to KDbg and choose Execution|Break. You've just caught the +nasty program in flagranti! +

+... achieve that the program passes over a breakpoint a number of times +before it stops?

+In the breakpoint list select the breakpoint; +then click Conditional and specify the number of times to skip the +breakpoint in the Ignore count field. +

+... set environment variables for the executable?

+Select Execution|Arguments and specify the environment variables +in the program arguments dialog. +

+... set a working directory for the executable?

+Select Execution|Arguments and specify the working directory in +the program arguments dialog. +

+... get rid of this terminal window?

+Select File|Settings and switch to the Output +tab. +Select Only output, simple terminal emulation and click +OK. +Now restart the program (choose it from the list under File|Recent Executables). +The program output goes now to the built-in output +window and stdin is redirected to /dev/null. +

You must do this for every new program that you debug. +

Important: You should not do this if your program expects +input from the terminal (usually stdin) or if its output requires nifty +terminal emulation (more than carriage-return and line-feed). The built-in +output window does not support input and terminal emulation. + + diff --git a/kdbg/doc/en/index.html b/kdbg/doc/en/index.html dissimilarity index 82% index c0041da..df2f7b1 100644 --- a/kdbg/doc/en/index.html +++ b/kdbg/doc/en/index.html @@ -1,247 +1,178 @@ - - - - - - KDbg - User's Manual - - - -

-KDbg - User's Manual

- -

-Contents

- - - -
-

-Introduction

-KDbg is a front-end for gdb, the GNU debugger. -

At the moment there is not much documentation available. -

For the really brave there's documentation about how KDbg -can understand types like QString. -

-What's it that I see here?

-The main window of KDbg consist of four panes: -

The upper left pane shows the source code. Mostly, source code -windows are opened automatically. To open a souce code window manually -choose File|Open Source from the menu. You can switch the opened -source code windows by choosing an open source file from the Window -menu. -

The lower left pane displays the backtrace (aka stack frames), -i.e. the functions that the program has entered, but not left yet. The -innermost frame (where the program currently executes) is shown at the -top. Click on a stack frame to inspect the variables of that frame. -

The upper right pane displays the local variables. Whenever the -progam stops, KDbg displays the values of the local variables in this pane. -

The lower right pane displays expressions of your choice (such -expression is also called a watch). To add an expression, type it -into the edit field and press Enter or click Add. To remove an expression, -click on it (choose the root of the expression) and click Del. -

The gearwheel in the toolbar indicates whether gdb is working, in which -case it rotates. It rotates fast while KDbg wouldn't accept execution commands, -and it rotates slowly while KDbg gets the variable values. -

-Using KDbg

-To debug a program, choose File|Executable from the menu. -The program is loaded. An xterm window is opened which will show -the output of the debuggee. If you want to debug a core dump, you -must first load the executable that produced the core dump, then choose -File|Core -Dump from the menu. Now KDbg goes to the point in the program that -caused the core dump. -

To run the program with arguments, set the working directory, -or set environment variables, choose Execution|Arguments. -See -below for more details. -

You can also choose program specific settings that apply only to a certain -executable using File|Settings. More... -

In the menu Execution you find the commands that you need to -run -the program, step through code, and to interrupt the program -(Break) while it is running. The important commands (Run -and all kinds of Step) are bound to function keys. For efficient -debugging I strongly recommend that you get used to using them. -
The functions are not configurable, but perhaps you want -to contribute a bit of code that does it? -

In the menu Breakpoint you find commands to set, clear, disable, -and enable permanent and temporary breakpoints. You can display -a list of active breakpoints. You can also set a breakpoint by clicking -at the left end of the source line (using the left mouse button), and you -can enable and disable a breakpoint by clicking it using the middle mouse -button. -

In the menu View you find commands to show and hide various windows. -These are docking windows, which means that you can drag them around and -arrange them in any manner you like. -

-The breakpoint list

-The breakpoint list can be displayed using View|Breakpoints. For -each breakpoint the following is shown: the breakpoint location, the hit -count, the ignore count if set, the condition if set. The icon in front -of the entry indicates whether the breakpoint is enabled (a red dot) or -disabled (a bright red dot), whether the breakpoint is temporary (a tiny -clock is overlaid) or whether the breakpoint is conditional (a tiny question -mark is overlaid). -

You can set a condition on a breakpoint (so that the program -is only stopped if the condition is true) or set an ignore count -(so that the program is not stopped the next n times that the breakpoint -is hit). To do that, press the Conditional button and enter the -condition and/or ignore count. -

-Specifying program arguments, working directory, -environment variables

-Choose Execution|Arguments to open a dialog where you can set program -arguments, the working directory for your program, and environment variables. -

In the top edit box enter the arguments that shall be passed on to your -program. Next time the program is started, the new arguments will be used. -

In the edit box below you can specify the working directory for your -program. The new working directory will be passed to gdb immediately, i.e. -gdb will work with the new setting as soon as you press OK. Your -program will use the new directory only when it is run the next time. -

In the environment variables section type in an expression of the form -VARIABLE=value -to set the environment variable VARIABLE to the value value, -and click Modify. To remove a variable, select it from the list -below and click Remove. To change the value, edit the value in the -edit field and click Modify. If you change the name of the variable -and click Modify, you add a new variable! The new environment variables -will be used by your program the next time it is run. -

An important environment variable to set if you are using glibc2 on -Linux is LD_BIND_NOW. It is very important that you set this variable -to 1 for all your debugging sessions. If it is not set, gdb cannot -step into and out of system functions that are imported from the shared -libc -and other libraries. -

-Global options

-To specify some global options, choose File|Global Options. You -can set the following: - - -

-How to invoke gdb

-If you want to use a different version of gdb, you can specify it under -How -to invoke GDB. The default command is gdb --fullname --nx. -Be sure to also specify these options if you change the gdb executable. -If you leave them away, KDbg will not work. If you messed up the entry, -you can clear it to revert to the default setting. -

-How to invoke a terminal emulator

-If you want to use a different terminal program to show the output of the -program, specify it under Terminal for program output. The default -setting is xterm -name kdbgio -title %T -e sh -c %C. In this entry, -%T -will be replaced by a title string, %C will be replaced by a Bourne -shell script that loops infinitely so that the terminal window doesn't -close. (No, it doesn't use CPU, it calls sleep 3600 in a loop -:) An alternative for this setting could be konsole -nowelcome -name -kdbgio -caption %T -e sh -c %C. -

-Pop into foreground

-You can specify whether the KDbg window shall move itself into the foreground -as soon as the program being debugged stops (at a breakpoint or due to -a signal). The KDbg window is not activated, however (at least under KWM, -the KDE window manager). Some users may feel that this behavior is intrusive, -so this option is off by default. -

If this option is on, KDbg will also retreat itself into the background -when the program is continued by any command, but it does so only after -a timeout that can be specified. This avoids that the debugger window flashes -back and fore each time you click any of the Step commands. -

-Tips and Tricks

- - - -

-Known problems

-gdb 4.16 has problems in handling C++ classes with virtual base classes. -(Such classes commonly occur in CORBA programs.) It dies quite often due -to a segmentation violation. KDbg reports when gdb exits unexpectedly. -Unfortunately, you cannot really do anything about it. You have to restart -gdb by choosing File|Executable, which restarts your debugging session -:-(. -

KDbg's type recognition only works for libraries that are linked dynamically -to the program being debugged. -

-Author

-KDbg is written by Johannes Sixt -with the help of many others. -
KDbg homepage at http://members.telecom.at/~johsixt/kdbg.html. - - + + + + + + + KDbg - User's Manual + + + +

+KDbg - User's Manual

+ +

+Contents

+ + + +
+

+Introduction

+KDbg is a front-end for gdb, the GNU debugger. +

This means that KDbg itself is not the debugger. Rather, it communicates +with gdb, a command line debugger, by sending commands to it and +receiving the output, such as variable values. The menu commands and mouse +clicks are translated into gdb commands, and the output of gdb +is translated into (more or less) visible information, such as structured +variable contents. +

The upshot of all this is that KDbg completely relies on the capabilities +of the underlying command line debugger, gdb. KDbg can do no more +than gdb can. For example, if you have a gdb that does +not supports debugging of threaded programs, KDbg cannot, either (even +though it offers a threads window). +

+Using KDbg

+Before you start using KDbg, you may want to review the options in the +Global Options dialog that you invoke +with File|Global Options. +

+Specifying a debugging target

+To debug a program, choose File|Executable from the menu. If you +have debugged the program earlier, you can choose it from File|Recent +Executables. The program is loaded. +

If you want to debug a core dump, you must first load the executable +that produced the core dump, then choose +File|Core Dump from the +menu. Now KDbg goes to the point in the program that caused the core dump. +

You can now set breakpoints, using the Breakpoint menu, the right +mouse button menu, or the breakpoint window. +

You can also choose program specific settings that apply only to the +currently loaded executable using File|Settings, in the Program +Settings dialog. +

+Running the program

+Now run the program by selecting Execution|Run. The program now +executes as usual until it either exits, hits a breakpoint or watchpoint, +or receives a signal. +

You can run the program with arguments, set a working directory, or +set environment variables. To do this, choose Execution|Arguments +and specify your options in the Program Arguments +dialog (before you start the program). +

You can also attach to a program that is currently running. To do this, +first load the executable file like above. Then choose Execution|Attach. +Specify the process number and click OK. The running program is +halted (not terminated), and the current point of execution is displayed +in the source window. +

+The program stopped - now what?

+When the program stops at a breakpoint, watchpoint, or due to a signal, +the source code window displays the line +where the program stopped. It is very common that the program stops due +to a signal (usually a SIGSEGV, segmentation violation) in a function +that is not part of the program, that you have written. In this case you +investigate the stack window and look for a function +that you have written (start at the top of the list) and click on it. This +will bring you to a location that you can start your search for the real +bug. +

In the menu Execution you find the commands that you need to +run +the program, step through code, and to interrupt the program (Break) +while it is running. The important commands (Run and all kinds of +Step) are bound to function keys. For efficient debugging it is +strongly recommend that you get used to using them. +
The functions are not configurable, but perhaps you want +to contribute a bit of code that does it? +

In the menu Breakpoint you find commands to set, clear, disable, +and enable permanent and temporary breakpoints. You can display a list +of breakpoints in the breakpoints window. +You can also set a breakpoint by clicking at the left end of the source +line (using the left mouse button), and you can enable and disable a breakpoint +by clicking it using the middle mouse button. +

The gearwheel in the toolbar indicates whether gdb is working, in which +case it rotates. It rotates fast while KDbg wouldn't accept execution commands, +and it rotates slowly while KDbg retrieves the values of variable. +

+KDbg's information windows

+KDbg displays information and accepts commands in number of different windows. +In the menu View you find commands to show and hide these windows. +They are docking windows, which means that you can drag them around and +arrange them in any manner you like. + + +

+Tips and such

+The following topics give some useful hints on using KDbg. + + +

+Known problems

+gdb 4.16 has problems in handling C++ classes with virtual base classes. +(Such classes commonly occur in CORBA programs.) It dies quite often due +to a segmentation violation. KDbg reports when gdb exits unexpectedly. +Unfortunately, you cannot really do anything about it. You have to restart +gdb by choosing File|Executable, which restarts your debugging session +:-(. +

KDbg's type recognition only works for libraries that are linked dynamically +to the program being debugged. +

+Author

+KDbg is written by Johannes Sixt +with the help of many others. +
KDbg homepage is at http://members.nextra.at/johsixt/kdbg.html. + + diff --git a/kdbg/doc/en/localvars.html b/kdbg/doc/en/localvars.html new file mode 100644 index 0000000..d14a237 --- /dev/null +++ b/kdbg/doc/en/localvars.html @@ -0,0 +1,21 @@ + + + + + + + KDbg - User's Manual - Local Variables + + +Contents +

+The Local Variables Window

+The local variables window is opened using View|Locals. The local +variables window displays the contents of the local variables at the currently +selected stack frame. +

The set of local variables that are displayed is determined by the stack +frame that is selected in the stack window. +

Variable values that changed between stops of the program are displayed +in red color. + + diff --git a/kdbg/doc/en/memory.html b/kdbg/doc/en/memory.html new file mode 100644 index 0000000..546deda --- /dev/null +++ b/kdbg/doc/en/memory.html @@ -0,0 +1,27 @@ + + + + + + + KDbg - User's Manual - Memory Dump + + +Contents +

+The Memory Dump Window

+The memory dump window is displayed using View|Memory. It displays +the contents of the program's memory at arbitrary adresses. +

To display memory contents, enter an address in the edit field. The +address need not be given in hexadecimal form - it can be an expression. +

You can specifiy a format how the memory contents shall be displayed +by chooseing the appropriate options from the popup menu that you invoke +by clicking the right mouse button. +

A number of address expressions are remembered. You can recall such +an expression from the drop-down list. Please note that the address expression +is remembered together with the format. +

If you don't need to investigate memory contents, it is recommended +that you clear the expression so that no memory dump is displayed - this +speeds up the debugging process. + + diff --git a/kdbg/doc/en/pgmoutput.html b/kdbg/doc/en/pgmoutput.html new file mode 100644 index 0000000..586caad --- /dev/null +++ b/kdbg/doc/en/pgmoutput.html @@ -0,0 +1,47 @@ + + + + + + + KDbg - User's Manual - Program Output + + +Contents +

+The Program Output Window

+The program output window is displayed using View|Output. The output +window captures text that is written to stdout and stderr by the program +being debugged. +

The output window does not allow to type input for the program and it +features only minimal terminal emulation: \n (line-feed) is treated +like a carriage-return-line-feed combination, and \r (carriage-return) +is ignored. These capabilities are usually sufficient to debug GUI programs +which only write debugging output to stdout and stderr. +

When a program is debugged with KDbg for the first time, the program +output window is not used. The reason for this is that KDbg cannot +know whether the program requires sophisticated terminal emulation or if +it expects input through a terminal. So, a terminal emulator program is +used by default. In order to redirect the output to the output window, +you must do the following: +

    +
  1. +Open the Settings dialog by selecting File|Settings.
    2. + +
  2. +Switch to the Output tab.
    3. + +
  3. +Choose Only output, simple terminal emulation and click OK.
    4. + +
  4. +Reload the program by selecting it from the list in File|Recent Executables.
    5. +
+You can clear the contents of the output window by selecting Clear +from the popup menu that appears when you click the right mouse button. +

If the last line of the output is visible, the window always scrolls +automatically so that the last line remains visible when new output arrives.. +If, however, you manually scroll up so that the last line is not visible, +the visible portion of text will not change. + + diff --git a/kdbg/doc/en/pgmsettings.html b/kdbg/doc/en/pgmsettings.html index 8919375..477a411 100644 --- a/kdbg/doc/en/pgmsettings.html +++ b/kdbg/doc/en/pgmsettings.html @@ -3,18 +3,22 @@ - + + KDbg - User's Manual - Program Settings - - + +Contents

-Program Settings

-In this dialog, program specific settings can be selected. The settings -apply only to the currently loaded executable and will be saved across -sessions. -

Important note: The chosen settings will only apply the -next time the executable is loaded into KDbg. This means that after pressing -OK in this dialog, you must reload the executable using File|Executable!! +The Program Settings Dialog +In this dialog, program specific settings can be selected. It is invoked +by File|Settings. The settings apply only to the currently loaded +executable and will be saved across sessions. +

Important note: The chosen settings will only +apply the next time the executable is loaded into KDbg. This means that +after pressing +OK in this dialog, you must reload the executable +using File|Executable!!
+