|
 |
e2e90d4 |
diff --git a/debug/org.eclipse.cdt.debug.application/scripts/README b/debug/org.eclipse.cdt.debug.application/scripts/README
|
|
|
e2e90d4 |
index 0bed384..b761e30 100644
|
|
|
e2e90d4 |
--- a/debug/org.eclipse.cdt.debug.application/scripts/README
|
|
|
e2e90d4 |
+++ b/debug/org.eclipse.cdt.debug.application/scripts/README
|
|
|
e2e90d4 |
@@ -3,15 +3,11 @@ is needed of the CDT plug-ins to debug a C/C++ executable. Build is not support
|
|
 |
48ea26a |
Editing is allowed, but you will need to rebuild outside the Stand-alone Debugger for
|
|
|
48ea26a |
those changes to manifest in your debugging session.
|
|
|
48ea26a |
|
|
|
48ea26a |
-To install the Stand-alone debugger locally in your $HOME directory, run the install.sh
|
|
 |
176ddf9 |
-script found in the scripts sub-directory of the plugins directory in your Eclipse installation:
|
|
|
176ddf9 |
+To run the Stand-alone debugger, use the /usr/bin/cdtdebug script. The first time the
|
|
|
176ddf9 |
+script is run, it will create an fcdtdebugger sub-directory in your $HOME directory. This
|
|
|
176ddf9 |
+directory will contain a config.ini file and a dev.properties file.
|
|
|
176ddf9 |
|
|
|
176ddf9 |
- ./install.sh
|
|
|
48ea26a |
-
|
|
|
48ea26a |
-The install script will create a cdtdebugger directory in your $HOME directory. This
|
|
|
48ea26a |
-directory will contain a config.ini file, a dev.properties file, and a cdtdebug.sh script.
|
|
|
43d9a9f |
-The cdtdebug.sh script will start the debugger from the command-line. The cdtdebug.sh script
|
|
|
43d9a9f |
-does not have to be located in the cdtdebugger directory and can be moved if you prefer.
|
|
|
48ea26a |
+The /usr/bin/cdtdebug script will start the debugger from the command-line.
|
|
|
48ea26a |
|
|
|
48ea26a |
The script takes a few options which are mentioned below:
|
|
|
48ea26a |
|
|
|
e2e90d4 |
@@ -55,8 +51,5 @@ If no -a or -e option is specified, the last executable debugged via -e will be
|
|
|
48ea26a |
debugging. Otherwise, if this is the first time, a dialog will be presented to enter
|
|
|
48ea26a |
an executable, build log, and program arguments.
|
|
|
48ea26a |
|
|
|
e2e90d4 |
- e.g. ~/cdtdebugger/cdtdebug.sh -b ~/build.log -e ~/myproject/bin/a.out arg1 arg2
|
|
|
176ddf9 |
-
|
|
|
176ddf9 |
-The cdtdebug.sh script that is found in the plug-in can also be run directly, but cannot
|
|
|
176ddf9 |
-be moved. The one installed in the cdtdebugger directory on the other hand, can be moved.
|
|
|
e2e90d4 |
+ e.g. cdtdebug -b ~/build.log ~/myproject/bin/a.out arg1 arg2
|
|
|
48ea26a |
|