diff --git a/debuggers/gdb/gdbconfigpage.ui b/debuggers/gdb/gdbconfigpage.ui
index 0cd658c508..4bfda1825e 100644
--- a/debuggers/gdb/gdbconfigpage.ui
+++ b/debuggers/gdb/gdbconfigpage.ui
@@ -1,315 +1,318 @@
GdbConfigPage
0
0
698
483
Debugger Configuration
-
Debugger
-
0
0
Debugger e&xecutable:
false
kcfg_gdbPath
-
-
+
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.
+
+ Override path to gdb executable
+
-
0
0
<html><head/><body><p>If you want gdb to be executed by a special shell script, which for example properly sets the library path, insert it here e.g.: /path/to/script.sh --scriptArguments</p><p>Note: your script'll be invoked like this: /path/to/script.sh --scriptArguments debugger --debuggerArguments. So script.sh <span style=" font-weight:600;">must</span> invoke "debugger" executable manually.</p></body></html>
She&ll script:
false
kcfg_debuggingShell
-
-
+
<html><head/><body><p>If you want gdb to be executed by a special shell script, which for example properly sets the library path, insert it here e.g.: /path/to/script.sh --scriptArguments</p><p>Note: your script'll be invoked like this: /path/to/script.sh --scriptArguments debugger --debuggerArguments. So script.sh <span style=" font-weight:600;">must</span> invoke "debugger" executable manually.</p></body></html>
<html><head/><body><p><br/></p></body></html>
-
Options
QFormLayout::ExpandingFieldsGrow
-
Display static &members:
kcfg_displayStaticMembers
-
Displaying static members makes GDB slower in
producing data within KDE and Qt.
It may change the "signature" of the data
which QString and friends rely on,
but if you need to debug into these values then
check this option.
-
Display &demangled names:
kcfg_asmDemangle
-
When displaying the disassembled code you
can select to see the methods' mangled names.
However, non-mangled names are easier to read.
-
S&tart Debugger with:
kcfg_startWith
-
-
Application Output
-
GDB Console
-
Frame Stack
-
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
Remote Debugging
-
<html><head/><body><p>Script to start remote application</p><p></p><p>This shell script is run after the Gdb Config script has been sourced by gdb.</p><p>It's purpose is to actually start the remote process.</p><p>1) Find a way to execute a command remotely - rsh, ssh, telnet, ...</p><p>2a) Execute "gdbserver ... application" on target.</p><p>or if your executable contains the gdb stub:</p><p>2b) Execute "application" on target.</p></body></html>
R&un shell script:
false
kcfg_runShellScript
-
-
+
<html><head/><body><p>Script to start remote application</p><p></p><p>This shell script is run after the Gdb Config script has been sourced by gdb.</p><p>It's purpose is to actually start the remote process.</p><p>1) Find a way to execute a command remotely - rsh, ssh, telnet, ...</p><p>2a) Execute "gdbserver ... application" on target.</p><p>or if your executable contains the gdb stub:</p><p>2b) Execute "application" on target.</p></body></html>
-
<html><head/><body><p>This script is sourced by gdb when the debugging starts.</p></body></html>
Gdb &config script:
false
kcfg_configGdbScript
-
-
+
<html><head/><body><p>Script to connect with remote application</p><p>For example:</p><p> shell sleep 5 #wait for remote program to start</p><p> target remote ... #connect to the remote debugger</p><p> continue #[optional] run debugging to the first breakpoint.</p></body></html>
-
<html><head/><body><p>Script to connect with remote application</p><p>For example:</p><p> shell sleep 5 #wait for remote program to start</p><p> target remote ... #connect to the remote debugger</p><p> continue #[optional] run debugging to the first breakpoint.</p></body></html>
Run &gdb script:
false
kcfg_runGdbScript
-
-
+
<html><head/><body><p>This script is sourced by gdb when the debugging starts.</p></body></html>
-
Qt::Vertical
20
40
KUrlRequester
- QFrame
+ QWidget
1
kcfg_gdbPath
kcfg_debuggingShell
kcfg_displayStaticMembers
kcfg_asmDemangle
kcfg_startWith
kcfg_configGdbScript
kcfg_runShellScript
kcfg_runGdbScript
kurlrequester.h
diff --git a/debuggers/lldb/widgets/lldbconfigpage.ui b/debuggers/lldb/widgets/lldbconfigpage.ui
index 1d55a6ab5f..0470cf4a27 100644
--- a/debuggers/lldb/widgets/lldbconfigpage.ui
+++ b/debuggers/lldb/widgets/lldbconfigpage.ui
@@ -1,226 +1,226 @@
LldbConfigPage
0
0
- 528
+ 530
535
Debugger Configuration
-
Debugger
-
Debugger executable:
-
-
-
- /path/to/lldb-mi/
+
+
+ Override path to lldb-mi executable
-
- Arguments:
+ Additional Arguments:
-
- Additional arguments passing to lldb
+
-
Environment:
-
-
0
0
-
-
Inherit system environment
-
Options
-
Config script:
-
-
-
+
+
/path/to/lldb/config/script
-
Start debugger with:
-
-
Application Output
-
LLDB Console
-
Frame Stack
-
Break on start:
-
-
- Re&mote Debugging
+ Remo&te Debugging
true
-
Remote server:
-
host:port
-
Remote work path:
-
/path/to/a/on-device/writable/directory
-
Qt::Vertical
20
149
KDevelop::EnvironmentConfigureButton
QToolButton
shell/environmentconfigurebutton.h
KDevelop::EnvironmentSelectionWidget
QComboBox
util/environmentselectionwidget.h
KUrlRequester
- QLineEdit
+ QWidget