mirror of
https://github.com/eclipse-cdt/cdt
synced 2025-04-23 22:52:11 +02:00
6acb6dbc70
- add org.eclipse.cdt.debug.application plugin which supports running CDT debugger as Eclipse application - add org.eclipse.cdt.debug.application.docs plugin which is the modified CDT docs - add org.eclipse.cdt.debug.standalone-feature which bundles the two aforementioned plugins - add org.eclipse.cdt.debug.standlone.source-feature Change-Id: I1a1ae855ab3912e678b7d9e3465e2fbbfe949e13 Reviewed-on: https://git.eclipse.org/r/25845 Reviewed-by: Jeff Johnston <jjohnstn@redhat.com> Tested-by: Jeff Johnston <jjohnstn@redhat.com>
53 lines
No EOL
2.6 KiB
Text
53 lines
No EOL
2.6 KiB
Text
The CDT Stand-alone Debugger brings up an minimal Eclipse instance which has all that
|
|
is needed of the CDT plug-ins to debug a C/C++ executable. Build is not supported.
|
|
Editing is allowed, but you will need to rebuild outside the Stand-alone Debugger for
|
|
those changes to manifest in your debugging session.
|
|
|
|
To install the Stand-alone debugger locally in your $HOME directory, run the install.sh
|
|
script directly from the scripts sub-directory of the plugins directory in your
|
|
Eclipse installation:
|
|
|
|
sh ./install.sh
|
|
|
|
The script uses relative directories so you cannot run the script from any other working directory.
|
|
|
|
The install script will create a cdtdebugger directory in your $HOME directory. This
|
|
directory will contain a config.ini file, a dev.properties file, and a cdtdebug.sh script.
|
|
The cdtdebug.sh script will start the debugger from the command-line. It does not
|
|
have relative directories so you can move it around as you like.
|
|
|
|
The script takes a few options which are mentioned below:
|
|
|
|
-data : workspace to use for your Eclipse session if you do not want the default
|
|
$HOME/workspace-gdbstandalone
|
|
|
|
-consoleLog : if you want error messages reported directly to the command console
|
|
|
|
-a : specify attaching to an existing executable on system. A dialog will
|
|
be brought up to allow you to select which one.
|
|
|
|
-b $PATH : path to build log for an executable. This will be used to figure out
|
|
include paths and compilation flags. This option assumes you will
|
|
be using the -e option described below.
|
|
|
|
-c $CPATH : path to core-file. This option must precede a -e option to specify an
|
|
executable.
|
|
|
|
-e $PATH [args...] : path to your executable to debug plus any optional command line
|
|
arguments to pass to main(). This option must be last and should
|
|
not precede any other arguments as they will be treated as arguments
|
|
to main.
|
|
|
|
If no -a or -e option is specified, the last executable debugged will be offered for
|
|
debugging. Otherwise, if this is the first time, a dialog will be presented to enter
|
|
an executable, build log, and program arguments.
|
|
|
|
e.g. sh ~/cdtdebugger/cdtdebug.sh -b ~/build.log ~/myproject/bin/a.out arg1 arg2
|
|
|
|
The cdtdebug.sh script that is found in the plug-in can also be run directly, but only
|
|
in this scripts directory as it uses relative directories to find the Eclipse instance and
|
|
the plugins directory.
|
|
|
|
e.g. sh ./cdtdebug.sh -b ~/build.log ~/myproject/bin/a.out arg1 arg2
|
|
|
|
|