mirrors/cdt
1
0
Fork 0
mirror of https://github.com/eclipse-cdt/cdt synced 2024-10-28 03:59:40 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Change standalone debugger to no longer limit number of bundles

Browse source 
The maintenance of having a streamlined standalone debugger that
starts as fast as possible is no longer possible. See for
example #591 - therefore when using standalone debugger, use
the same sets of plug-ins/features as the product it is installed
in uses. The side effect is that the standalone debugger in this
use case will start slower and extra "stuff" will be present in
this UI.

For people just building the standalone debugger, provide a minimum
feature set. This will be many more bundles than before, but
should still provide a reasonably small set that starts well.

This simplification also includes removing the the duplicates set
of CDT docs (debug/org.eclipse.cdt.debug.application.doc). These
provided a simplified version of CDT's documentation targetted
at just standalone debugger. However there are a few problems related
to this duplication:

- The two sets of docs were not kept in sync
- The standalone docs appear in the online help, leading to
  duplicated entries
- With the config.ini changes above, there is no way to exclude
  the main docs in the standalone case, so remove the duplicate

A number of directly related clean-ups are included too:

- Remove the `ConfigGenerator.java` that stopped being referenced
  in PR #761
- Complete the removal of `build-standalone-debugger-rcp` profile
  that was started in #761. There is a small drawback to not having
  this profile, the standalone debugger is very slow to build
  compared to the rest of CDT. If this becomes a problem, restoring
  this profile along with the changes made in #761 is reasonable.
- bring debug.product's licenses up to date
- modernize command line args to eclipse when using debug.product

Fixes #781
This commit is contained in:
Jonah Graham 2024-05-10 10:18:07 -04:00
parent 5f2fcd0f19
commit 0568568c33
688 changed files with 192 additions and 22695 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
.github/workflows/build-test.yml vendored
View file

@ -47,7 +47,6 @@ jobs:
clean verify -B -V \ clean verify -B -V \
-Dmaven.test.failure.ignore=true \ -Dmaven.test.failure.ignore=true \
-DexcludedGroups=flakyTest,slowTest \ -DexcludedGroups=flakyTest,slowTest \
-P build-standalone-debugger-rcp \
-Ddsf.gdb.tests.timeout.multiplier=50 \ -Ddsf.gdb.tests.timeout.multiplier=50 \
-Ddsf-gdb.skip.tests=$(test ${{ steps.filter.outputs.dsf }} == 'false' && echo 'true' || echo 'false') \ -Ddsf-gdb.skip.tests=$(test ${{ steps.filter.outputs.dsf }} == 'false' && echo 'true' || echo 'false') \
-Dindexer.timeout=300 -Dindexer.timeout=300

5
BUILDING.md
View file

@ -38,11 +38,6 @@ Individual p2 repos can be turned on and off to allow building CDT, or parts of
- test CDT against a pre-built CDT by using the cdtRepo profile. - test CDT against a pre-built CDT by using the cdtRepo profile.
- build the standalone rcp debugger against the latest simrel `mvn verify -DuseSimrelRepo -f debug/org.eclipse.cdt.debug.application.product` - build the standalone rcp debugger against the latest simrel `mvn verify -DuseSimrelRepo -f debug/org.eclipse.cdt.debug.application.product`
#### build-standalone-debugger-rcp
Using the `build-standalone-debugger-rcp` profile will include the standalone debugger, located
in `debug/org.eclipse.cdt.debug.application.product`
#### skip-all-tests, skip-tests-except-cdt-ui, skip-tests-except-dsf-gdb, skip-tests-except-cdt-other #### skip-all-tests, skip-tests-except-cdt-ui, skip-tests-except-dsf-gdb, skip-tests-except-cdt-other
Using any of the above profiles can skip large sets of tests. The CI build uses this to parallelize tests. See https://ci.eclipse.org/cdt/view/Gerrit/ Using any of the above profiles can skip large sets of tests. The CI build uses this to parallelize tests. See https://ci.eclipse.org/cdt/view/Gerrit/

1
Jenkinsfile vendored
View file

@ -48,7 +48,6 @@ pipeline {
-Ddsf.gdb.tests.timeout.multiplier=50 \ -Ddsf.gdb.tests.timeout.multiplier=50 \
-Dindexer.timeout=300 \ -Dindexer.timeout=300 \
-P production \ -P production \
-P build-standalone-debugger-rcp \
-Ddsf.gdb.tests.gdbPath=/shared/common/gdb/gdb-all/bin \ -Ddsf.gdb.tests.gdbPath=/shared/common/gdb/gdb-all/bin \
-Dcdt.tests.dsf.gdb.versions=gdb.10,gdbserver.10 \ -Dcdt.tests.dsf.gdb.versions=gdb.10,gdbserver.10 \
-Dmaven.repo.local=/home/jenkins/.m2/repository \ -Dmaven.repo.local=/home/jenkins/.m2/repository \

1
debug/org.eclipse.cdt.debug.application.doc/.gitignore vendored
View file

@ -1 +0,0 @@
/workspace/

22
debug/org.eclipse.cdt.debug.application.doc/.project
View file

@ -1,22 +0,0 @@
<?xml version="1.0" encoding="UTF-8"?>
<projectDescription>
<name>org.eclipse.cdt.debug.application.doc</name>
<comment></comment>
<projects>
</projects>
<buildSpec>
<buildCommand>
<name>org.eclipse.pde.ManifestBuilder</name>
<arguments>
</arguments>
</buildCommand>
<buildCommand>
<name>org.eclipse.pde.SchemaBuilder</name>
<arguments>
</arguments>
</buildCommand>
</buildSpec>
<natures>
<nature>org.eclipse.pde.PluginNature</nature>
</natures>
</projectDescription>

2
debug/org.eclipse.cdt.debug.application.doc/.settings/org.eclipse.core.resources.prefs
View file

@ -1,2 +0,0 @@
eclipse.preferences.version=1
encoding/<project>=UTF-8

184
debug/org.eclipse.cdt.debug.application.doc/.settings/org.eclipse.pde.api.tools.prefs
View file

@ -1,184 +0,0 @@
ANNOTATION_ELEMENT_TYPE_ADDED_CLASS_BOUND=Error
ANNOTATION_ELEMENT_TYPE_ADDED_FIELD=Error
ANNOTATION_ELEMENT_TYPE_ADDED_INTERFACE_BOUND=Error
ANNOTATION_ELEMENT_TYPE_ADDED_INTERFACE_BOUNDS=Error
ANNOTATION_ELEMENT_TYPE_ADDED_METHOD=Error
ANNOTATION_ELEMENT_TYPE_ADDED_METHOD_WITHOUT_DEFAULT_VALUE=Error
ANNOTATION_ELEMENT_TYPE_ADDED_TYPE_MEMBER=Error
ANNOTATION_ELEMENT_TYPE_ADDED_TYPE_PARAMETER=Error
ANNOTATION_ELEMENT_TYPE_CHANGED_CLASS_BOUND=Error
ANNOTATION_ELEMENT_TYPE_CHANGED_CONTRACTED_SUPERINTERFACES_SET=Error
ANNOTATION_ELEMENT_TYPE_CHANGED_INTERFACE_BOUND=Error
ANNOTATION_ELEMENT_TYPE_CHANGED_INTERFACE_BOUNDS=Error
ANNOTATION_ELEMENT_TYPE_CHANGED_RESTRICTIONS=Error
ANNOTATION_ELEMENT_TYPE_CHANGED_TO_CLASS=Error
ANNOTATION_ELEMENT_TYPE_CHANGED_TO_ENUM=Error
ANNOTATION_ELEMENT_TYPE_CHANGED_TO_INTERFACE=Error
ANNOTATION_ELEMENT_TYPE_CHANGED_TYPE_CONVERSION=Error
ANNOTATION_ELEMENT_TYPE_REMOVED_CLASS_BOUND=Error
ANNOTATION_ELEMENT_TYPE_REMOVED_FIELD=Error
ANNOTATION_ELEMENT_TYPE_REMOVED_INTERFACE_BOUND=Error
ANNOTATION_ELEMENT_TYPE_REMOVED_METHOD=Error
ANNOTATION_ELEMENT_TYPE_REMOVED_METHOD_WITHOUT_DEFAULT_VALUE=Error
ANNOTATION_ELEMENT_TYPE_REMOVED_METHOD_WITH_DEFAULT_VALUE=Error
ANNOTATION_ELEMENT_TYPE_REMOVED_TYPE_MEMBER=Error
ANNOTATION_ELEMENT_TYPE_REMOVED_TYPE_PARAMETER=Error
ANNOTATION_ELEMENT_TYPE_REMOVED_TYPE_PARAMETERS=Error
API_COMPONENT_ELEMENT_TYPE_REMOVED_API_TYPE=Error
API_COMPONENT_ELEMENT_TYPE_REMOVED_REEXPORTED_API_TYPE=Error
API_COMPONENT_ELEMENT_TYPE_REMOVED_REEXPORTED_TYPE=Error
API_COMPONENT_ELEMENT_TYPE_REMOVED_TYPE=Error
API_USE_SCAN_FIELD_SEVERITY=Error
API_USE_SCAN_METHOD_SEVERITY=Error
API_USE_SCAN_TYPE_SEVERITY=Error
CLASS_ELEMENT_TYPE_ADDED_CLASS_BOUND=Error
CLASS_ELEMENT_TYPE_ADDED_FIELD=Error
CLASS_ELEMENT_TYPE_ADDED_INTERFACE_BOUND=Error
CLASS_ELEMENT_TYPE_ADDED_INTERFACE_BOUNDS=Error
CLASS_ELEMENT_TYPE_ADDED_METHOD=Error
CLASS_ELEMENT_TYPE_ADDED_RESTRICTIONS=Error
CLASS_ELEMENT_TYPE_ADDED_TYPE_PARAMETER=Error
CLASS_ELEMENT_TYPE_CHANGED_CLASS_BOUND=Error
CLASS_ELEMENT_TYPE_CHANGED_CONTRACTED_SUPERCLASS_SET=Error
CLASS_ELEMENT_TYPE_CHANGED_CONTRACTED_SUPERINTERFACES_SET=Error
CLASS_ELEMENT_TYPE_CHANGED_DECREASE_ACCESS=Error
CLASS_ELEMENT_TYPE_CHANGED_INTERFACE_BOUND=Error
CLASS_ELEMENT_TYPE_CHANGED_NON_ABSTRACT_TO_ABSTRACT=Error
CLASS_ELEMENT_TYPE_CHANGED_NON_FINAL_TO_FINAL=Error
CLASS_ELEMENT_TYPE_CHANGED_RESTRICTIONS=Error
CLASS_ELEMENT_TYPE_CHANGED_SUPERCLASS=Error
CLASS_ELEMENT_TYPE_CHANGED_TO_ANNOTATION=Error
CLASS_ELEMENT_TYPE_CHANGED_TO_ENUM=Error
CLASS_ELEMENT_TYPE_CHANGED_TO_INTERFACE=Error
CLASS_ELEMENT_TYPE_CHANGED_TYPE_CONVERSION=Error
CLASS_ELEMENT_TYPE_REMOVED_CLASS_BOUND=Error
CLASS_ELEMENT_TYPE_REMOVED_CONSTRUCTOR=Error
CLASS_ELEMENT_TYPE_REMOVED_FIELD=Error
CLASS_ELEMENT_TYPE_REMOVED_INTERFACE_BOUND=Error
CLASS_ELEMENT_TYPE_REMOVED_INTERFACE_BOUNDS=Error
CLASS_ELEMENT_TYPE_REMOVED_METHOD=Error
CLASS_ELEMENT_TYPE_REMOVED_SUPERCLASS=Error
CLASS_ELEMENT_TYPE_REMOVED_TYPE_MEMBER=Error
CLASS_ELEMENT_TYPE_REMOVED_TYPE_PARAMETER=Error
CLASS_ELEMENT_TYPE_REMOVED_TYPE_PARAMETERS=Error
CONSTRUCTOR_ELEMENT_TYPE_ADDED_CLASS_BOUND=Error
CONSTRUCTOR_ELEMENT_TYPE_ADDED_INTERFACE_BOUND=Error
CONSTRUCTOR_ELEMENT_TYPE_ADDED_INTERFACE_BOUNDS=Error
CONSTRUCTOR_ELEMENT_TYPE_ADDED_TYPE_PARAMETER=Error
CONSTRUCTOR_ELEMENT_TYPE_CHANGED_CLASS_BOUND=Error
CONSTRUCTOR_ELEMENT_TYPE_CHANGED_DECREASE_ACCESS=Error
CONSTRUCTOR_ELEMENT_TYPE_CHANGED_INTERFACE_BOUND=Error
CONSTRUCTOR_ELEMENT_TYPE_CHANGED_NON_ABSTRACT_TO_ABSTRACT=Error
CONSTRUCTOR_ELEMENT_TYPE_CHANGED_NON_FINAL_TO_FINAL=Error
CONSTRUCTOR_ELEMENT_TYPE_CHANGED_NON_STATIC_TO_STATIC=Error
CONSTRUCTOR_ELEMENT_TYPE_CHANGED_STATIC_TO_NON_STATIC=Error
CONSTRUCTOR_ELEMENT_TYPE_CHANGED_TYPE_PARAMETER=Error
CONSTRUCTOR_ELEMENT_TYPE_CHANGED_VARARGS_TO_ARRAY=Error
CONSTRUCTOR_ELEMENT_TYPE_REMOVED_ANNOTATION_DEFAULT_VALUE=Error
CONSTRUCTOR_ELEMENT_TYPE_REMOVED_CLASS_BOUND=Error
CONSTRUCTOR_ELEMENT_TYPE_REMOVED_INTERFACE_BOUND=Error
CONSTRUCTOR_ELEMENT_TYPE_REMOVED_INTERFACE_BOUNDS=Error
CONSTRUCTOR_ELEMENT_TYPE_REMOVED_TYPE_PARAMETER=Error
CONSTRUCTOR_ELEMENT_TYPE_REMOVED_TYPE_PARAMETERS=Error
ENUM_ELEMENT_TYPE_CHANGED_CONTRACTED_SUPERINTERFACES_SET=Error
ENUM_ELEMENT_TYPE_CHANGED_RESTRICTIONS=Error
ENUM_ELEMENT_TYPE_CHANGED_TO_ANNOTATION=Error
ENUM_ELEMENT_TYPE_CHANGED_TO_CLASS=Error
ENUM_ELEMENT_TYPE_CHANGED_TO_INTERFACE=Error
ENUM_ELEMENT_TYPE_CHANGED_TYPE_CONVERSION=Error
ENUM_ELEMENT_TYPE_REMOVED_ENUM_CONSTANT=Error
ENUM_ELEMENT_TYPE_REMOVED_FIELD=Error
ENUM_ELEMENT_TYPE_REMOVED_METHOD=Error
ENUM_ELEMENT_TYPE_REMOVED_TYPE_MEMBER=Error
FIELD_ELEMENT_TYPE_ADDED_VALUE=Error
FIELD_ELEMENT_TYPE_CHANGED_DECREASE_ACCESS=Error
FIELD_ELEMENT_TYPE_CHANGED_FINAL_TO_NON_FINAL_STATIC_CONSTANT=Error
FIELD_ELEMENT_TYPE_CHANGED_NON_FINAL_TO_FINAL=Error
FIELD_ELEMENT_TYPE_CHANGED_NON_STATIC_TO_STATIC=Error
FIELD_ELEMENT_TYPE_CHANGED_STATIC_TO_NON_STATIC=Error
FIELD_ELEMENT_TYPE_CHANGED_TYPE=Error
FIELD_ELEMENT_TYPE_CHANGED_VALUE=Error
FIELD_ELEMENT_TYPE_REMOVED_TYPE_ARGUMENT=Error
FIELD_ELEMENT_TYPE_REMOVED_TYPE_ARGUMENTS=Error
FIELD_ELEMENT_TYPE_REMOVED_VALUE=Error
ILLEGAL_EXTEND=Warning
ILLEGAL_IMPLEMENT=Warning
ILLEGAL_INSTANTIATE=Warning
ILLEGAL_OVERRIDE=Warning
ILLEGAL_REFERENCE=Warning
INTERFACE_ELEMENT_TYPE_ADDED_CLASS_BOUND=Error
INTERFACE_ELEMENT_TYPE_ADDED_DEFAULT_METHOD=Error
INTERFACE_ELEMENT_TYPE_ADDED_FIELD=Error
INTERFACE_ELEMENT_TYPE_ADDED_INTERFACE_BOUND=Error
INTERFACE_ELEMENT_TYPE_ADDED_INTERFACE_BOUNDS=Error
INTERFACE_ELEMENT_TYPE_ADDED_METHOD=Error
INTERFACE_ELEMENT_TYPE_ADDED_RESTRICTIONS=Error
INTERFACE_ELEMENT_TYPE_ADDED_SUPER_INTERFACE_WITH_METHODS=Error
INTERFACE_ELEMENT_TYPE_ADDED_TYPE_MEMBER=Error
INTERFACE_ELEMENT_TYPE_ADDED_TYPE_PARAMETER=Error
INTERFACE_ELEMENT_TYPE_ADDED_TYPE_PARAMETERS=Error
INTERFACE_ELEMENT_TYPE_CHANGED_CLASS_BOUND=Error
INTERFACE_ELEMENT_TYPE_CHANGED_CONTRACTED_SUPERINTERFACES_SET=Error
INTERFACE_ELEMENT_TYPE_CHANGED_INTERFACE_BOUND=Error
INTERFACE_ELEMENT_TYPE_CHANGED_INTERFACE_BOUNDS=Error
INTERFACE_ELEMENT_TYPE_CHANGED_RESTRICTIONS=Error
INTERFACE_ELEMENT_TYPE_CHANGED_TO_ANNOTATION=Error
INTERFACE_ELEMENT_TYPE_CHANGED_TO_CLASS=Error
INTERFACE_ELEMENT_TYPE_CHANGED_TO_ENUM=Error
INTERFACE_ELEMENT_TYPE_CHANGED_TYPE_CONVERSION=Error
INTERFACE_ELEMENT_TYPE_REMOVED_CLASS_BOUND=Error
INTERFACE_ELEMENT_TYPE_REMOVED_FIELD=Error
INTERFACE_ELEMENT_TYPE_REMOVED_INTERFACE_BOUND=Error
INTERFACE_ELEMENT_TYPE_REMOVED_INTERFACE_BOUNDS=Error
INTERFACE_ELEMENT_TYPE_REMOVED_METHOD=Error
INTERFACE_ELEMENT_TYPE_REMOVED_TYPE_MEMBER=Error
INTERFACE_ELEMENT_TYPE_REMOVED_TYPE_PARAMETER=Error
INVALID_ANNOTATION=Ignore
INVALID_JAVADOC_TAG=Error
INVALID_REFERENCE_IN_SYSTEM_LIBRARIES=Warning
LEAK_EXTEND=Warning
LEAK_FIELD_DECL=Warning
LEAK_IMPLEMENT=Warning
LEAK_METHOD_PARAM=Warning
LEAK_METHOD_RETURN_TYPE=Warning
METHOD_ELEMENT_TYPE_ADDED_CLASS_BOUND=Error
METHOD_ELEMENT_TYPE_ADDED_INTERFACE_BOUND=Error
METHOD_ELEMENT_TYPE_ADDED_INTERFACE_BOUNDS=Error
METHOD_ELEMENT_TYPE_ADDED_RESTRICTIONS=Error
METHOD_ELEMENT_TYPE_ADDED_TYPE_PARAMETER=Error
METHOD_ELEMENT_TYPE_CHANGED_CLASS_BOUND=Error
METHOD_ELEMENT_TYPE_CHANGED_DECREASE_ACCESS=Error
METHOD_ELEMENT_TYPE_CHANGED_INTERFACE_BOUND=Error
METHOD_ELEMENT_TYPE_CHANGED_NON_ABSTRACT_TO_ABSTRACT=Error
METHOD_ELEMENT_TYPE_CHANGED_NON_FINAL_TO_FINAL=Error
METHOD_ELEMENT_TYPE_CHANGED_NON_STATIC_TO_STATIC=Error
METHOD_ELEMENT_TYPE_CHANGED_STATIC_TO_NON_STATIC=Error
METHOD_ELEMENT_TYPE_CHANGED_TYPE_PARAMETER=Error
METHOD_ELEMENT_TYPE_CHANGED_VARARGS_TO_ARRAY=Error
METHOD_ELEMENT_TYPE_REMOVED_ANNOTATION_DEFAULT_VALUE=Error
METHOD_ELEMENT_TYPE_REMOVED_CLASS_BOUND=Error
METHOD_ELEMENT_TYPE_REMOVED_INTERFACE_BOUND=Error
METHOD_ELEMENT_TYPE_REMOVED_INTERFACE_BOUNDS=Error
METHOD_ELEMENT_TYPE_REMOVED_TYPE_PARAMETER=Error
METHOD_ELEMENT_TYPE_REMOVED_TYPE_PARAMETERS=Error
MISSING_EE_DESCRIPTIONS=Warning
TYPE_PARAMETER_ELEMENT_TYPE_ADDED_CLASS_BOUND=Error
TYPE_PARAMETER_ELEMENT_TYPE_ADDED_INTERFACE_BOUND=Error
TYPE_PARAMETER_ELEMENT_TYPE_CHANGED_CLASS_BOUND=Error
TYPE_PARAMETER_ELEMENT_TYPE_CHANGED_INTERFACE_BOUND=Error
TYPE_PARAMETER_ELEMENT_TYPE_REMOVED_CLASS_BOUND=Error
TYPE_PARAMETER_ELEMENT_TYPE_REMOVED_INTERFACE_BOUND=Error
UNUSED_PROBLEM_FILTERS=Warning
automatically_removed_unused_problem_filters=false
changed_execution_env=Error
eclipse.preferences.version=1
incompatible_api_component_version=Error
incompatible_api_component_version_include_major_without_breaking_change=Disabled
incompatible_api_component_version_include_minor_without_api_change=Disabled
incompatible_api_component_version_report_major_without_breaking_change=Warning
incompatible_api_component_version_report_minor_without_api_change=Warning
invalid_since_tag_version=Error
malformed_since_tag=Error
missing_since_tag=Error
report_api_breakage_when_major_version_incremented=Disabled
report_resolution_errors_api_component=Warning

36
debug/org.eclipse.cdt.debug.application.doc/.settings/org.eclipse.pde.prefs
View file

@ -1,36 +0,0 @@
compilers.f.unresolved-features=1
compilers.f.unresolved-plugins=1
compilers.incompatible-environment=1
compilers.p.build=1
compilers.p.build.bin.includes=1
compilers.p.build.encodings=2
compilers.p.build.java.compiler=2
compilers.p.build.java.compliance=1
compilers.p.build.missing.output=2
compilers.p.build.output.library=1
compilers.p.build.source.library=1
compilers.p.build.src.includes=0
compilers.p.deprecated=1
compilers.p.discouraged-class=1
compilers.p.exec-env-too-low=1
compilers.p.internal=1
compilers.p.missing-packages=2
compilers.p.missing-version-export-package=2
compilers.p.missing-version-import-package=2
compilers.p.missing-version-require-bundle=2
compilers.p.no-required-att=0
compilers.p.no.automatic.module=1
compilers.p.not-externalized-att=1
compilers.p.service.component.without.lazyactivation=1
compilers.p.unknown-attribute=1
compilers.p.unknown-class=0
compilers.p.unknown-element=1
compilers.p.unknown-identifier=0
compilers.p.unknown-resource=0
compilers.p.unresolved-ex-points=0
compilers.p.unresolved-import=0
compilers.s.create-docs=false
compilers.s.doc-folder=doc
compilers.s.open-tags=1
compilers.use-project=true
eclipse.preferences.version=1

7
debug/org.eclipse.cdt.debug.application.doc/META-INF/MANIFEST.MF
View file

@ -1,7 +0,0 @@
Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: %bundleName
Bundle-SymbolicName: org.eclipse.cdt.debug.application.doc;singleton:=true
Bundle-Version: 11.6.0.qualifier
Bundle-Vendor: %provider
Bundle-Localization: plugin

38
debug/org.eclipse.cdt.debug.application.doc/about.html
View file

@ -1,38 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
<title>About</title>
</head>
<body lang="EN-US">
<h2>About This Content</h2>
<p>November 30, 2017</p>
<h3>License</h3>
<p>
The Eclipse Foundation makes available all content in this plug-in
(&quot;Content&quot;). Unless otherwise indicated below, the Content
is provided to you under the terms and conditions of the Eclipse
Public License Version 2.0 (&quot;EPL&quot;). A copy of the EPL is
available at <a href="https://www.eclipse.org/legal/epl-2.0">https://www.eclipse.org/legal/epl-2.0</a>.
For purposes of the EPL, &quot;Program&quot; will mean the Content.
</p>
<p>
If you did not receive this Content directly from the Eclipse
Foundation, the Content is being redistributed by another party
(&quot;Redistributor&quot;) and different terms and conditions may
apply to your use of any object code in the Content. Check the
Redistributor's license that was provided with the Content. If no such
license exists, contact the Redistributor. Unless otherwise indicated
below, the terms and conditions of the EPL still apply to any source
code in the Content and such source code may be obtained at <a
href="https://www.eclipse.org/">https://www.eclipse.org</a>.
</p>
</body>
</html>

61
debug/org.eclipse.cdt.debug.application.doc/book.css
View file

@ -1,61 +0,0 @@
/* following font face declarations need to be removed for DBCS */
body, h1, h2, h3, h4, p, table, td, caption, th, ul, ol, dl, li, dd, dt {font-family: Arial, sans-serif; color: #000000}
pre { font-family: Courier, monospace}
/* end font face declarations */
/* following font size declarations should be OK for DBCS */
body, h1, h2, h3, h4, p, table, td, caption, th, ul, ol, dl, li, dd, dt {font-size: 12pt; }
pre { font-size: 12pt}
/* end font size declarations */
body { background: #FFFFFF}
h1 { font-size: 18pt; margin-top: 5; margin-bottom: 1 }
h2 { font-size: 14pt; margin-top: 25; margin-bottom: 3 }
h3 { font-size: 12pt; margin-top: 20; margin-bottom: 3 }
h4 { font-size: 10pt; margin-top: 20; margin-bottom: 3; font-style: italic }
p { font-size: 12pt; }
pre { margin-left: 6; font-size: 9pt }
a:link { color: #006699 }
a:visited { color: #996699 }
a:hover { color: #006699 }
ul { margin-top: 0; margin-bottom: 10 }
li { margin-top: 0; margin-bottom: 0 }
li p { margin-top: 0; margin-bottom: 0 }
ol { margin-top: 0; margin-bottom: 10 }
dl { margin-top: 0; margin-bottom: 10 }
dt { margin-top: 0; margin-bottom: 0; font-weight: bold }
dd { margin-top: 0; margin-bottom: 0 }
strong { font-weight: bold}
em { font-style: italic}
var { font-style: italic}
div.revision { border-left-style: solid; border-left-width: thin;
border-left-color: #7B68EE; padding-left:5 }
th { font-weight: bold }
.title {
font-size: 20px; font-weight: bold;
}
/* Mike Behm's addition to the style sheet */
.userinput { font-family: monospace; }
.guitab, .important, .guibutton, .selectblue, .guimenu, .guilabel,
.notetitle {
color: #000000;
font-family: helvetica, arial, sans-serif;
font-weight: bold;
}
div.linux {display:none;}
.firsterm {font-style:italic;}
.typewriter {font-family:monospace;}
.bold {font-weight:600;}
.linethrough {text-decoration: line-through;}
.underline {text-decoration: underline;}

15
debug/org.eclipse.cdt.debug.application.doc/build.properties
View file

@ -1,15 +0,0 @@
bin.includes = plugin.xml,\
META-INF/,\
html/,\
images/,\
reference/,\
concepts/,\
book.css,\
notices.html,\
tasks/,\
about.html,\
testToc.xml,\
toc.xml,\
index/,\
plugin.properties
src.includes = about.html

71
debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_before_you_begin.htm
View file

@ -1,71 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Before you begin</title>
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<div role="main">
<h1>Before you begin</h1>
<p>Depending on how you obtained the Stand-alone Debugger, you might have also received
a toolchain.
However, if you downloaded the Stand-alone Debugger from the Eclipse web site, then you will require a toolchain before
you can debug any projects.</p>
<p>The Stand-alone Debugger uses plug-ins from the CDT (C/C++ Development Tools) project pertaining to
debugging an application. These CDT debugging components require some GNU toolchain elements such as
the gdb debugger and gcc compiler. The Stand-alone Debugger does allow editing files but does not support rebuilding
a project; a user can do that outside of the Stand-alone Debugger either either from the command line or using
the full CDT IDE which supports edit/compile/build/debug.
<p>Each platform that runs the Stand-alone Debugger requires different steps to acquire the GNU toolchain.</p>
<h2>Windows</h2>
<p>For windows, MinGW and Cygwin are the two main platform choices for acquiring the GNU toolchain.
It is important to understand the difference between them.
Cygwin produces executables that use the Cygwin POSIX runtime. Note that this runtime is GPL licensed.
MinGW produces native Windows executables that do not require a separate runtime.</p>
<ul>
<li><p>For <strong>MinGW</strong>, it is recommended to use the MinGW installer, mingw-get, to manage your
MinGW installation. Download and run the latest mingw-get-inst package from the
<a href="https://sourceforge.net/projects/mingw/files">MinGW Downloads page.</a>
</p>
<p>Note that the Wascana IDE has been discontinued.</p>
</li>
<li><p><strong>Cygwin</strong> can be installed from the Cygwin site at
<a href="https://www.cygwin.com">https://www.cygwin.com</a>. You need to manually select
the gdb and gcc packages. The gcc package is used to figure out default include paths
and built-in macros for indexing the code for navigation purposes.</p>
</li>
<li><p>The <strong>Windows SDK</strong> provides the Visual C++ compiler and header files and libraries required
to create Windows applications.</p>
<p><i>Note:</i> For this release, the integration should be considered beta quality. It is not recommended for
production use.</p>
</li>
</ul>
<h2>Linux</h2>
<p>All Linux distributions include the GNU toolchain. They may not, however, be installed by default.
For instructions about installing the GNU toolchain for Linux, see the instructions for your particular distribution.</p>
<h2>Mac OS X</h2>
The Stand-alone Debugger supports the Apple GNU toolchain that is included in with the Xcode IDE. It can be downloaded
from the Apple's developer site, <a href="https://developer.apple.com/">https://developer.apple.com</a>
<h2>Other Platforms</h2>
<p>The GNU toolchain is supported on all platforms that the Stand-alone Debugger supports. For instructions about installing the GNU toolchain
on your platform, see your platform vendor.</p>
<p><img src="../images/ng00_04a.gif" ALT="QNX Copyright Statement" >
</p>
</div>
</body>
</html>

63
debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_brkpnts.htm
View file

@ -1,63 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Breakpoints</title>
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<div role="main">
<h1>Breakpoints</h1>
<p>A breakpoint suspends the execution of a program at the location where the breakpoint is set.
To set a line breakpoint, right-click in the marker bar area on the left side of an editor beside
the line where you want the program to be suspended, then choose <strong>Toggle Breakpoint</strong>. You can
also double-click on the marker bar next to the source code line. A new breakpoint marker appears
on the marker bar, directly to the left of the line where you added the breakpoint. Also, the new
breakpoint appears in the Breakpoints view list.
</p>
<p>Once set, a breakpoint can be enabled and disabled by right-clicking on its icon or by
right-clicking on its description in the <strong>Breakpoints</strong> view.
</p>
<ul>
<li>When a breakpoint is enabled, it causes the program to suspend whenever it is hit.
Enabled breakpoints are indicated with a blue
<img src="../images/icon_breakpoint_obj.gif" alt="enabled breakpoint" > circle.
Enabled breakpoints that are successfully installed
are indicated with a checkmark <img src="../images/installed_ovr.gif" alt="checkmark overlay" > overlay.</li>
<li>When a breakpoint is disabled, it will not affect the execution of the program.
Disabled breakpoints are indicated with a white
<img src="../images/icon_breakpoint_disable.gif" alt="disabled breakpoint" > circle.<br>
<img src="../images/add_breakpoint.png" ALT="Editor view with cursor highlighting breakpoint" width="453" height="335">
</li>
</ul>
<p><strong>Note: </strong>Execution will also suspend
if <strong>Stop at main() on startup</strong> is enabled
on the <strong>Launch Configuration</strong> dialog.
To access the <strong>Launch Configuration</strong> dialog,
from the menu bar choose <strong>Run > Debug</strong>.
</p>
<hr>
<p><img src="../images/ngref.gif" ALT="Related reference" width="143" height="21">
<br>
<a href="../reference/cdt_o_views.htm">Run menu</a><br>
<a href="../reference/cdt_o_views.htm">Breakpoints view</a>
</p>
<p>
<img src="../images/rh03_04.gif" ALT="Red Hat Statement"><br>
<img src="../images/ng00_04a.gif" ALT="IBM Copyright Statement">
</p>
</div>
</body>
</html>

162
debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_build_over.htm
View file

@ -1,162 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Building C/C++ projects</title>
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<div role="main">
<h1>Building C/C++ projects</h1>
<p>The CDT relies on an external make utility, such as GNU make, to
build a project. The CDT can generate makefiles automatically when you
create a Managed Make C project or a Managed Make C++ project. You have
the option of creating a Standard Make C project or a Standard Make C++
project and providing the makefile yourself.</p>
<h2>Required utilities</h2>
<p>You must install and configure the following utilities:
</p>
<ul>
<li>Build (e.g. make).</li>
<li>Compile (e.g. gcc).</li>
<li>Debug (e.g. gdb).</li>
</ul>
<strong>Note: </strong> while make, gcc and gdb are the examples used in the
documentation, virtually any similar set of tools or utilities could be
used.
<p></p>
<p><strong>Tip: </strong>Cygwin contains these utilities (make, gcc and gdb) for
a Windows environment.&nbsp; While running the cygwin installation,
ensure <span class="typewriter">gcc</span> and <span class="typewriter">make</span> are selected since they are not
installed by default. For more information, see <a
href="https://www.cygwin.com">https://www.cygwin.com</a>. If you are a
Red Hat user, all that you need to do to build your project is included
in the Red Hat Linux installation.
For other operating systems, please refer to your installation
documentation.</p>
<p></p>
<h2>Build terminology</h2>
<p>The CDT uses a number of terms to describe the scope of the build. </p>
<h3>Build Project</h3>
<p>This is an incremental build (make all, assuming all is defined in
your makefile). Only the components affected by modified files in that
particular project are built.</p>
<h3>Rebuild Project</h3>
<p>Builds every file in the project whether or not a file has been
modified since the last build. A rebuild is a clean followed by a build.</p>
<p>For more information on builds, see:</p>
<ul>
<li><strong>Workbench User Guide &gt; Concepts &gt; Workbench &gt; Builds</strong></li>
<li><strong>Workbench User Guide &gt; Tasks &gt; Building resources</strong></li>
</ul>
<p>Build-related information is displayed as follows:</p>
<ul>
<li>The Console view displays the output of the build tools.</li>
<li>The Problems view displays a list of compiler errors and warnings
related to your projects.</li>
<li>For Standard Make projects, the Makefile targets are displayed in
the Make Targets view.</li>
</ul>
<p>For more information about the Problems view, see <strong>Workbench User
Guide &gt; Reference &gt; User interface information &gt; Views and
editors &gt; Problems view</strong>.</p>
<h2>Getting a makefile</h2>
<p>You can either create a C/C++ project for which you supply the <strong>makefile</strong>
or create a C/C++ project for which the CDT generates makefiles
automatically.</p>
<p>To create a new project, from the menu bar choose <strong>File &gt; New
&gt; Project</strong>. In the dialog that appears, expand the C/C++ group
and choose e.g. C Project</p>
<ul>
<li>In the resulting wizard page, to create a project for which you supply the <strong>makefile</strong>,
select <strong>Makefile project</strong> and choose one of the alternatives under that.
An empty project, or a simple "Hello World" can be created.
You edit and manage the makefile yourself.
<p>&nbsp;</p>
</li>
<li>To create a project for which the CDT supplies a basic <strong>makefile</strong>,
select another project type, e.g. <strong>Executable</strong> and choose one of the examples
under that, or choose <strong>Empty Project</strong>.
</li>
</ul>
<h2>Setting build preferences</h2>
<p>You can set build preferences in Eclipse:</p>
<dl>
<dt>Build order</dt>
<dd>If certain projects must be built before others, you can set the <em>build
order</em>. If your project refers to another project, the CDT must
build the other project first. To set the build order, from the menu
bar select <strong>Window &gt; Preferences</strong> and choose <strong> General > Preferences > Build Order</strong>.
<p>When you set the build order, the CDT does not rebuild projects
that depend on a project; you must rebuild all projects to ensure all
changes are propagated.</p>
</dd>
<dt>Automatic save</dt>
<dd>You can set the CDT to perform an <em>automatic save</em> of all
modified resources when you perform a manual build. In the preferences dialog,
select <strong>General > Workspace</strong> and check <strong>Save automatically before build</strong>.
By default,
this feature is <em>not</em> enabled.</dd>
</dl>
<h2>Controlling the building of your project</h2>
<p>For a Makefile project, the C/C++ compiler that a project uses
is controlled by the project's <strong>Properties</strong> setting.
To view a project's properties, right-click on the project and select <strong>Properties</strong>.
In the dialog that appears, the <strong>C/C++ Build</strong>
page enables you to control a variety of settings, including:</p>
<dl>
<dt>Build Command</dt>
<dd>On the <strong>Builder Settings</strong> tab, this controls which <code>make</code> is used. To change it, uncheck <strong>Use
default build command</strong> and change it or add arguments to the make command.</dd>
<dt>Build Setting</dt>
<dd>On the <strong>Behaviour</strong> tab, this controls whether the compiler will <strong>Stop on first build error</strong> or not
(keep going). Unchecking <strong>Stop on first build error</strong> will force the compiler to attempt to build all referenced
projects even if the current project has errors.</dd>
<dt>Workbench Build Behavior</dt>
<dd>On the <strong>Behaviour </strong> tab, this controls which makefile target will be built depending on the scope of the
build, e.g. <code>all</code> or <code>clean</code>.</dd>
</dl>
<p>For a standard (non-Makefile) project (often called "Managed Build" or "Managed Make" project from
earlier CDT version), the project properties dialog enables
you to manage the build configurations of your project. For additional
information see:</p>
<ul>
<li><strong>Reference &gt; C/C++ Properties &gt; C/C++ Project Properties &gt; Managed Make
Projects</strong></li>
<li><strong>Reference &gt; C/C++ Properties &gt; C/C++ Project Properties &gt; Managed Make File
Properties</strong></li>
</ul>
<h2>Viewing build information</h2>
<p>Build-related information is displayed as follows: </p>
<ul>
<li>The <strong>Console</strong> view displays the output of the make utility.</li>
<li>The <strong>Problems</strong> view displays a list of compiler errors and
warnings related to your projects. </li>
<li>For a Standard Make project, build actions display in the <strong>Make
Targets</strong> view.</li>
</ul>
<p><img src="../images/ngconcepts.gif" alt="Related concepts"
width="143" height="21">
<br>
<a href="cdt_c_projects.htm">CDT Projects</a><br>
<a href="cdt_c_proj_file_views.htm">Project file views</a></p>
<p><img src="../images/ngtasks.gif" alt="Related tasks"
width="143" height="21">
<br>
<a href="../tasks/cdt_o_build_task.htm">Building projects</a></p>
<p><img src="../images/ngref.gif" alt="Related reference"
width="143" height="21">
<br>
<a href="../reference/cdt_u_properties.htm">Project Properties</a></p>
&nbsp;
<p><img src="../images/rh03_04.gif" alt="Red Hat Copyright Statement"><br>
<img src="../images/ng00_04a.gif" alt="IBM Copyright Statement">
</p>
</div>
</body>
</html>

66
debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_comments.htm
View file

@ -1,66 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Comments</title>
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<div role="main">
<h1>Comments</h1>
<p>Comments are lines in a source file that have been marked to be ignored by the compiler.
Two styles of comments are supported by current C/C++ compilers:</p>
<ul>
<li><samp>/* text */</samp></li>
<li><samp>// text</samp></li>
</ul>
<h2>Comment</h2>
<p>You can quickly comment out one or more lines of code by inserting the leading
characters <samp>//</samp> at the beginning of the line. To do so, select the line
(or lines) of code you want to comment out and press <strong>CTRL+/</strong> (slash).</p>
<h2>Uncomment</h2>
<p>To uncomment select the line (or lines) of code, and press <strong>CTRL+\</strong>
(backslash).
<p><strong>Tip:</strong> The characters <samp>/* */</samp> on lines that are
already commented out, are not affected when you comment and uncomment code.</p>
<h2>Multiline comment</h2>
<p>You can use the Content Assist feature to insert a multi-line comment before a function.
Type <span class="typewriter">com+Ctrl+Space</span>, and the following code is entered at the cursor location:
<br><pre>
/*
* author userid
*
* To change this generated comment edit the template variable "comment":
* Window > Preferences > C/C++ > Editor > Templates.
*/
</pre>
To change the default comment click <strong>Window > Preferences > C > Templates</strong>. For more information see the
<a href="cdt_c_content_assist.htm">Content Assist</a> section.
<p><img src="../images/ngconcepts.gif" ALT="Related concepts" width="143" height="21">
<br>
<a href="cdt_c_content_assist.htm">Content Assist and code completion</a></p>
<p><img src="../images/ngtasks.gif" ALT="Related tasks" width="143" height="21">
<br>
<a href="../tasks/cdt_t_cust_cpp_editor.htm">Customizing the C++ editor</a><br>
<a href="../tasks/cdt_t_comment_out.htm">Commenting out code</a></p>
<p><img src="../images/ngref.gif" ALT="Related reference" width="143" height="21">
<br>
<a href="../reference/cdt_o_ceditor_pref.htm">C/C++ editor preferences</a></p>
<p>
<img src="../images/rh03_04.gif" ALT="Red Hat Copyright Statement"><br>
<img src="../images/ng00_04a.gif" ALT=" IBM Copyright Statement" >
</p>
</div>
</body>
</html>

98
debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_content_assist.htm
View file

@ -1,98 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Content Assist</title>
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<div role="main">
<h1>Content Assist</h1>
<p>Content Assist is a set of tools built into the CDT that can reduce the number of keystrokes you must
type to create your code. The Content Assist plug-in consists of several components that forecast what
a developer will type, based on the current context, scope, and prefix.</p>
<h2>Code completion</h2>
<p>Content assist provides code completion anywhere in the document. For the current project a list is
displayed of the elements that begin with the letter combination you entered, and
the relevance of each proposal is determined in the following order:</p>
<ul>
<li>Fields</li>
<li>Variables</li>
<li>Methods</li>
<li>Functions</li>
<li>Classes</li>
<li>Structs</li>
<li>Unions</li>
<li>Namespaces</li>
<li>Enumerations</li>
</ul>
You trigger the Code completion feature when you call Content Assist (such as when you type <span class="typewriter">Ctrl+Space</span>), but it is auto-activated when you type
<Q><strong>.</strong></Q>, <Q><strong>-></strong></Q> or <Q><strong>::</strong></Q>.</p>
<p><img src="../images/contentAssist_example.png" alt="C++ example showing Code Assist popup"></p>
<p>You can view the signature of each item on the list in a pop-up by pointing to it. You can then select an item in the list to insert it directly into your code. </p>
<h2>Templates</h2>
<p>You can create and save templates for frequently used sections of code, which will be inserted according to scope. The Content Assist feature also provides quick access to code
templates.</p>
<p>When you enter a letter combination in the C/C++ editor, and type <span class="typewriter">CTRL+SPACE</span> (or right-click and click <strong>Content Assist</strong>), a
list of code elements and templates that start with the letter combination that you typed is displayed.</p>
<p>You can then select a template from the list and it is inserted directly into your code.</p>
<img src="../images/editor_c_codetemplates_use.png" alt="C++ example showing Code Assist popup"></p>
<p>For example, the template <samp>do while statement</samp> contains the following code:</p>
<p><img src="../images/codetemplates_example.png" alt="Code Template showing do-while example"></p>
<p> When you select the <samp>do</samp> template from the list, you insert the following code:</p>
<p><pre>do {
} while (condition);</pre></p>
<p>If the completion engine finds only one proposal in your templates, that proposal is inserted at the current cursor position.
For example if you create a new .cpp file and type <span class="typewriter">mai+CTRL+SPACE</span> the following code is inserted at the cursor location:</p>
<p><pre>int
main(int argc, char **argv) {
}</pre></p>
<h2>No Completions</h2>
<p>If you invoke Content Assist, but no completions are found a message will be displayed on the status to inform you that the Content Assist parser has timed out.</p>
<p><img src="../images/cdt_ca_no_completions.png" alt="Content Assist No completions available message"></p>
<p><img src="../images/ngconcepts.gif" ALT="Related concepts" width="143" height="21">
<br>
<a href="cdt_o_code_entry.htm">Code entry</a></p>
<p><img src="../images/ngtasks.gif" ALT="Related tasks" width="143" height="21">
<br>
<a href="../tasks/cdt_t_contentassist.htm">Using Content Assist</a><br>
<a href="../tasks/cdt_t_add_codetemp.htm">Creating and editing templates</a><br>
<a href="../tasks/cdt_t_imp_code_temp.htm">Importing and exporting templates</a></p>
<p><img src="../images/ngref.gif" ALT="Related reference" width="143" height="21">
<br>
<a href="../reference/cdt_u_icons.htm">C/C++ perspective icons</a></p>
<p>
<img src="../images/ng00_04a.gif" ALT="IBM Copyright Statement" ></p>
</div>
</body>
</html>

89
debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_dbg_info.htm
View file

@ -1,89 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
<meta name="ProgId" content="FrontPage.Editor.Document">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Debug information</title>
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<div role="main">
<h1>Debug information</h1>
<p>When using the Stand-alone Debugger, you will be using the <strong>Debug</strong>
perspective. The <strong>Debug</strong> perspective lets you manage the debugging or running of a program
in the Eclipse Workbench. You can control the execution of your program by setting
breakpoints, suspending launched programs, stepping through your code, and
examining the contents of variables.</p>
<p>&nbsp;The <strong>Debug</strong> perspective displays the following information:</p>
<ul>
<li>The stack frame for the suspended threads
for each target that you are debugging</li>
<li>Each thread in your program represented as a node in the tree</li>
<li>The process for each program that you are running</li>
</ul>
<p>The <strong>Debug</strong> perspective also drives the <strong>C/C++ Editor</strong>. As you step
through your program, the <strong>C/C++ Editor</strong> highlights the location of the
execution pointer. </p>
<h2>Variables</h2>
<p>You can view information about the variables in a selected stack frame in the
Variables view. When execution stops, the changed values are
by default highlighted in red. Like the other debug-related views, the Variables view does
not refresh as you run your executable. A refresh occurs when execution stops.</p>
<h2>Expressions</h2>
<p>An expression is a snippet of code that can be evaluated to produce a result.
The context for an expression depends on the particular debug model. Some
expressions may need to be evaluated at a specific location in the program so
that the variables can be referenced. You can view information about expressions
in the Expressions view.</p>
<h2>Registers</h2>
<p>You can view information about the registers in a selected stack frame.
Values that have changed are highlighted in the Registers view when your program
stops.</p>
<h2>Memory</h2>
<p>You can inspect and change your process memory.</p>
<h2>Disassembly</h2>
<p>You can view disassembled code mixed with source information.</p>
<h2>Modules</h2>
<p>You can view information about the modules (executables and shared libraries) loaded
in the current debug session.</p>
<h2>Signals</h2>
<p>You can view the signals defined on the selected debug target and how the
debugger handles each one.</p>
<p><img src="../images/ngconcepts.gif" ALT="Related concepts" width="143" height="21">
<br>
<a href="cdt_c_over_cdt.htm">Overview of the CDT</a><br>
<a href="cdt_c_over_dbg.htm">Debug overview</a></p>
<p><img src="../images/ngtasks.gif" ALT="Related tasks" width="143" height="21">
<br>
<a href="../tasks/cdt_o_debug.htm">Debugging</a><br>
&nbsp;</p>
<p><img src="../images/ngref.gif" ALT="Related reference" width="143" height="21">
<br>
<a href="../reference/cdt_o_run_dbg_pages.htm">Run and Debug dialog box</a><br>
<a href="../reference/cdt_o_dbg_view.htm">Debug views</a></p><p>
<img src="../images/ng00_04a.gif" ALT="IBM Copyright Statement" > </p>
</div>
</body>
</html>

54
debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_discovery_options.htm
View file

@ -1,54 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Views in the C/C++ perspective</title>
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<div role="main">
<h1>Discovery options</h1>
<p>For projects where the IDE generates a makefile to build the project automatically, the IDE has more information about the internal build state of the make project compared to those projects where you provide a makefile to build the project.
<p>For example, a makefile includes build information and other settings, such as include file paths (-I) and macro definitions (-D), which are standard to the build tools (such as the compiler and linker). When the makefile is automatically created for you, this information is known to Eclipse to a greater extent then when you create and manage the makefile for a project yourself. The type of information affects the search capabilities and Code Assist abilities of Eclipse. Therefore, in this example, the purpose of Discovery Options is for improved search and Code Assist capability for projects where Eclipse does not manage the makefile for you. For example, in an open source file of an editor view, to see the declaration for a function that the code calls, you select the function, right click, and select <strong>Open Declaration</strong> from the context menu. If the location of the include file (that was coded in the makefile for the project) containing the function declaration was in some directory, the CDT would not find the declaration because it has no visibility for that include path. Consequently, you can use Discovery Options in the CDT to enhance the IDE build state by parsing the build process output to extract build path information that the CDT searching mechanism uses to locate and open the include file. By default, the CDT uses GNU* tools (gcc, etc.). If you want to build your projects using another compiler, use the settings described here.</p>
<p>Scanner configuration discovery is tightly linked to project's build process. The first part of scanner discovery begins during the make build for make projects where you provide the makefile. The Eclipse CDT parses the build output for compiler commands with options that specify the definition of the preprocessor symbols and include search paths (for the gcc compiler, -D and -I), and then it stores the information as the project's discovered scanner configuration.
<p>Next, after the build process completes, it is implemented as a separate Eclipse builder where it runs a generate scanner info command, and then parses the output (properties specified on the Discover Options tab for Builds in the Project Properties window).
<p>For C++, the default generate scanner information command is <strong>gcc -E -P -v myfile.c | myfile.cpp</strong>. This command reads the compiler's configuration file and prints the information that includes compiler's internally defined preprocessor symbols and include search paths.
<p>A single scanner configuration is applicable to all the files in a project. Although Eclipse discovers the information for each compilation unit, it stores the scanner configuration on a per project basis. This means that Eclipse applies a single, cumulative scanner configuration to all files in a project.
<p>The following situations identify circumstances when certain parts of the scanner configuration are in conflict:
<ul>
<li>Symbol definitions that contradict
<li>An incorrect order for the include paths
<li>Internal scanner information may not be applicable to all the files in a project (for a single compiler), because some files might be compiled with a different compiler, or have target specific options specified.
</ul>
</p>
<p><strong>Note:</strong> Only basic command line options are supported. In addition, only basic scanner configuration related command line options are recognized (for example, -D and -I for gcc). For some of the commands, their relative position in the command line is important. For information about these options, see the documentation for the utilities you are using.
<p><img src="../images/ngconcepts.gif" ALT="Related concepts" width="143" height="21">
<br><a href="cdt_c_over_cdt.htm">CDT Overview</a>
<br><a href="cdt_c_perspectives.htm">C/C++ perspectives</a>
</p>
<p><img src="../images/ngref.gif" ALT="Related reference" width="143" height="21">
<br><a href="../reference/cdt_o_views.htm">Views</a>
</p>
<p>
<img src="../images/rh03_04.gif" ALT="Red Hat Copyright Statement"><br>
<img src="../images/ng00_07.gif" ALT=" IBM Copyright Statement" >
</p>
</div>
</body>
</html>

53
debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_editor.htm
View file

@ -1,53 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>C/C++ editor</title>
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<div role="main">
<h1>C/C++ editor</h1>
<p>The Stand-alone Debugger provides an editor that gives you specific support for editing C/C++ code.
This C/C++ editor is invoked automatically when you open a C/C++ source file. While you are able
to modify the contents of a file, if you save those changes, you will need to rebuild the project outside of the Stand-alone Debugger
to synchronize the debug information in the executable with the source files used.</p>
<p>The C/C++ editor includes the following features:</p>
<ul>
<li>Syntax highlighting</li>
<li>Content/code assist</li>
<li>Code folding</li>
<li>Integrated debugging features</li>
</ul>
<p>You can customize some of the operation of the Editor view from the <strong>Window &gt; Preferences &gt; C/C++ &gt; Editor</strong> preferences dialog.</p>
<p><img src="../images/ngconcepts.gif" ALT="Related concepts" width="143" height="21">
<br><a href="cdt_c_over_cdt.htm">CDT Overview</a>
</p>
<p><img src="../images/ngtasks.gif" ALT="Related tasks" width="143" height="21">
<br><a href="../tasks/cdt_t_contentassist.htm">Using Content Assist</a>
</p>
<p><img src="../images/ngref.gif" ALT="Related reference" width="143" height="21">
<br><a href="../reference/cdt_o_ceditor_pref.htm">C/C++ editor preferences</a>
<br><a href="../reference/cdt_u_outline_view.htm">Outline view for C/C++</a>
<br><a href="../reference/cdt_o_views.htm">Views and editors</a>
</p>
<p>
<img src="../images/rh03_04.gif" ALT="Red Hat Copyright Statement"><br>
<img src="../images/ng00_07.gif" ALT=" IBM Copyright Statement" >
</p>
</div>
</body>
</html>

59
debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_indexer.htm
View file

@ -1,59 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>C/C++ Indexer</title>
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<div role="main">
<h1>C/C++ Indexer</h1>
<p>The C/C++ indexer uses the parser to create a database of your
source and header files that provides the basis for C/C++ search,
navigation features and parts of content assist.</p>
<p>The indexer runs on a background thread and reacts to resource
change events such as:
</p>
<ul>
<li>C/C++ project creation/deletion</li>
<li>Source files creation/deletion</li>
<li>File imports</li>
<li>Source file content changes</li>
</ul>
<p>It is possible to customize the behavior of the indexer through the
use of source folders or even turn it off completely. This customizable
behavior is available on a per-project basis (i.e. it is possible to
have different indexer settings for each project in your workspace). <br>
</p>
<p>CDT supports the contribution of additional indexers, with 2
indexers being provided with the default CDT release:<br>
</p>
<ul>
<li>Fast C/C++ Indexer : provides fastest indexing capabilities - both
declarations and cross reference information. This is the recommended indexer.<br>
</li>
<li>Full C/C++ Indexer : provides even more accurate indexing capabilities at the cost of performance - both
declarations and cross reference information.<br>
</li>
</ul>
<p><img src="../images/ngconcepts.gif" alt="Related concepts" width="143" height="21"><br>
<a href="cdt_c_search.htm">C/C++ search</a><br>
<a href="cdt_c_indexer_prog_bar.htm">C/C++ Indexer Progress Bar</a><br>
<a href="../concepts/cdt_c_scanner_discovery.htm">Scanner Discovery</a><br>
</p>
<p><img src="../images/ngtasks.gif" alt="Related tasks" width="143" height="21"><br>
<a href="../tasks/cdt_t_sel_search.htm">Selection Searching for C/C++ elements</a><br>
<a href="../tasks/cdt_t_set_src_fold.htm">Setting Source Folders</a><br>
</p>
<p><img src="../images/ngref.gif" alt="Related reference" width="143" height="21"><br>
<a href="../reference/cdt_u_search.htm">C/C++ search page, Search dialog box</a><br>
<a href="../reference/cdt_u_prop_general_idx.htm">C/C++ Project Properties, Indexer</a><br>
</p>
<p>&nbsp;</p>
<img src="../images/ng00_07.gif" alt="IBM Copyright Statement"
style="width: 324px; height: 14px;">
</div>
</body>
</html>

47
debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_indexer_fullindexer.htm
View file

@ -1,47 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html lang="en">
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Full C/C++ Indexer</title>
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<div role="main">
<h1>Full C/C++ Indexer</h1>
<p>The Full C/C++ Indexer is a new indexer for CDT 3.0 which makes use
of the new DOM. It creates a full index of the project's source
providing both declaration and cross reference information to the
various clients that make use of the index. In comparison with the
previous versions of the indexer, the new C/C++ indexer provides
quicker and more accurate results.<br>
</p>
<p>This indexer provides the most complete set of information but can
be potentially long running, especially on larger projects. <br>
</p>
<p><img src="../images/ngconcepts.gif" alt="Related concepts"
width="143" height="21"> <br>
<a href="cdt_c_indexer.htm">C/C++ Indexer</a><br>
<a href="cdt_c_search.htm">C/C++ search</a><br>
<a href="cdt_c_indexer_prog_bar.htm">C/C++ Indexer Progress Bar</a></p>
<p><img src="../images/ngtasks.gif" alt="Related tasks"
width="143" height="21"><br>
<a href="../tasks/cdt_t_sel_search.htm">Selection Searching for C/C++
elements</a><br>
<a href="../tasks/cdt_t_set_src_fold.htm">Setting Source Folders</a><br>
</p>
<p><img src="../images/ngref.gif" alt="Related reference"
width="143" height="21">
<br>
<a href="../reference/cdt_u_search.htm">C/C++ search page, Search
dialog box</a>
<br>
<a href="../reference/cdt_u_prop_general_idx.htm">C/C++ Project Properties, Indexer</a>
</p>
<p>&nbsp;</p>
<img style="width: 324px; height: 14px;" src="../images/ng00_07.gif"
alt="IBM Copyright Statement">
</div>
</body>
</html>

46
debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_indexer_prog_bar.htm
View file

@ -1,46 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<meta content="en-us" http-equiv="Content-Language">
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
<title>C/C++ Indexer Progress Bar</title>
<link href="../help.css" type="text/css" rel="stylesheet">
</head>
<body>
<div role="main">
<h1>C/C++ Indexer Progress Bar</h1>
<p>The indexer progress bar shows the progress status of the indexing
jobs in the progress views.</p>
<p>The indexing jobs can be temporarily paused by pressing the stop
button on the progress bar. This will cause the indexer to wait until
the next time the user runs a search job or makes a change to an
indexed element (by such actions as modifying an existing source file,
deleting a file, creating a new file, moving file and so on). The
indexer at this point will resume with the previously postponed
indexing job before moving on to the new one.</p>
<p>If you wish to cease indexing all together, you can cancel an
indexing job and disable the indexer through the properties.</p>
<p><img height="21" width="143" alt="Related concepts"
src="../images/ngconcepts.gif" >
<br>
<a href="cdt_c_search.htm">C/C++ search</a><br>
<a href="cdt_c_indexer.htm">C/C++ Indexer</a><br>
<p><img height="21" width="143" alt="Related tasks"
src="../images/ngtasks.gif" ><br>
<a href="../tasks/cdt_t_sel_search.htm">Selection Searching for C/C++
elements</a><br>
<a href="../tasks/cdt_t_set_src_fold.htm">Setting Source Folders</a><br>
</p>
<p><img height="21" width="143" alt="Related reference"
src="../images/ngref.gif" >
<br>
<a href="../reference/cdt_u_search.htm">C/C++ search page, Search
dialog box</a>
<br>
<a href="../reference/cdt_u_prop_general_idx.htm">C/C++ Project Properties, Indexer</a>
</p>
<p>&nbsp;</p>
<img alt="IBM Copyright Statement" src="../images/ng00_07.gif">
</div>
</body>
</html>

187
debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_makefile.htm
View file

@ -1,187 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Makefile</title>
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<div role="main">
<h1>Makefile</h1>
<p>A makefile is a text file that is referenced by the make command that describes the building of targets, and contains information such as source-level dependencies and build-order dependencies. </p>
<p>The CDT can generate a makefile for you, such projects are called Managed Make projects. Some projects, known as Standard Make projects, allow you to define your own makefile.</p>
<h2>Sample Makefile</h2>
<pre>
# A sample Makefile
# This Makefile demonstrates and explains
# Make Macros, Macro Expansions,
# Rules, Targets, Dependencies, Commands, Goals
# Artificial Targets, Pattern Rule, Dependency Rule.
# Comments start with a # and go to the end of the line.
# Here is a simple Make Macro.
LINK_TARGET = test_me.exe
# Here is a Make Macro that uses the backslash to extend to multiple lines.
# This allows quick modification of more object files.
OBJS = \
Test1.o \
Test2.o \
Main.o
# Here is a Make Macro defined by two Macro Expansions.
# A Macro Expansion may be treated as a textual replacement of the Make Macro.
# Macro Expansions are introduced with $ and enclosed in (parentheses).
REBUILDABLES = $(OBJS) $(LINK_TARGET)
# Make Macros do not need to be defined before their Macro Expansions,
# but they normally should be defined before they appear in any Rules.
# Consequently Make Macros often appear first in a Makefile.
# Here is a simple Rule (used for "cleaning" your build environment).
# It has a Target named "clean" (left of the colon ":" on the first line),
# no Dependencies (right of the colon),
# and two Commands (indented by tabs on the lines that follow).
# The space before the colon is not required but added here for clarity.
clean :
rm -f $(REBUILDABLES)
echo Clean done
# There are two standard Targets your Makefile should probably have:
# "all" and "clean", because they are often command-line Goals.
# Also, these are both typically Artificial Targets, because they don't typically
# correspond to real files named "all" or "clean".
# The rule for "all" is used to incrementally build your system.
# It does this by expressing a dependency on the results of that system,
# which in turn have their own rules and dependencies.
all : $(LINK_TARGET)
echo All done
# There is no required order to the list of rules as they appear in the Makefile.
# Make will build its own dependency tree and only execute each rule only once
# its dependencies' rules have been executed successfully.
# Here is a Rule that uses some built-in Make Macros in its command:
# $@ expands to the rule's target, in this case "test_me.exe".
# $^ expands to the rule's dependencies, in this case the three files
# main.o, test1.o, and test2.o.
$(LINK_TARGET) : $(OBJS)
g++ -g -o $@ $^
# Here is a Pattern Rule, often used for compile-line.
# It says how to create a file with a .o suffix, given a file with a .cpp suffix.
# The rule's command uses some built-in Make Macros:
# $@ for the pattern-matched target
# $lt; for the pattern-matched dependency
%.o : %.cpp
g++ -g -o $@ -c $&lt;
# These are Dependency Rules, which are rules without any command.
# Dependency Rules indicate that if any file to the right of the colon changes,
# the target to the left of the colon should be considered out-of-date.
# The commands for making an out-of-date target up-to-date may be found elsewhere
# (in this case, by the Pattern Rule above).
# Dependency Rules are often used to capture header file dependencies.
Main.o : Main.h Test1.h Test2.h
Test1.o : Test1.h Test2.h
Test2.o : Test2.h
# Alternatively to manually capturing dependencies, several automated
# dependency generators exist. Here is one possibility (commented out)...
# %.dep : %.cpp
# g++ -M $(FLAGS) $&lt; &gt; $@
# include $(OBJS:.o=.dep)
</pre>
<h2>Frequently Asked Questions:</h2>
Your Console view can be very useful for debugging a build.
<p><strong>Q1. My Console view says <span class="typewriter"><Q>Error launching builder</Q></span>. What does that mean?</strong></p>
<pre>
Error launching builder (make -k clean all )
(Exec error:Launching failed)
</pre>
<p>Most probably, the build command (by default "make") is not on your path. You can put it on your path and restart Eclipse.<br>
You can also change the build command to something that is on your path. If you are using MinGW tools to compile, you should replace the build command with "mingw32-make".</p>
<p><strong>Q2. My Console view says <span class="typewriter"><Q>No rule to make target 'X'</Q></span>.</strong></p>
<pre>
make -k clean all
make: *** No rule to make target 'clean'.
make: *** No rule to make target 'all'.
</pre>
<p>By default, the make program looks for a file most commonly called "Makefile" or "makefile".
If it cannot find such a file in the working directory, or if that file is empty or the file does not
contain rules for the command line goals ("clean" and "all" in this case), it will normally fail
with an error message similar to those shown. </p>
<p>If you already have a valid Makefile, you may need to change the working directory of your build. The default working directory for the build command is the project's root directory. You can change this by specifying an alternate Build Directory in the Make Project properties.
Or, if your Makefile is named something else (eg. <span class="typewriter">buildFile.mk</span>), you can specify the name by setting the default Build command to <span class="typewriter">make -f buildFile.mk</span>.</p>
<p>If you do not have a valid Makefile, create a new file named Makefile in the root directory. You can then add the contents of the sample Makefile (above), and modify it as appropriate.</p>
<p><strong>Q3. My Console view says <span class="typewriter">"missing separator"</span>.</strong></p>
<pre>
make -k clean all
makefile:12: *** missing separator. Stop.
</pre>
<p>The standard syntax of Makefiles dictates that every line in a build rule must be preceded by a Tab character.
This Tab character is often accidentally replaced with spaces, and because both result in white-space indentation,
this problem is easily overlooked. In the sample provided, the error message can be pinpointed to line 12 of the
file "makefile"; to fix the problem, insert a tab at the beginning of that line.</p>
<p><strong>Q4. My Console view says <span class="typewriter"><Q>Target 'all' not remade because of errors</Q></span>.</strong></p>
<pre>
make -k clean all
make: *** [clean] Error 255
rm -f Test1.o Test2.o Main.o test_me.exe
g++ -g -o Test1.o -c Test1.cpp
make: *** [Test1.o] Error 255
make: *** [Test2.o] Error 255
make: *** [Main.o] Error 255
g++ -g -o Test2.o -c Test2.cpp
g++ -g -o Main.o -c Main.cpp
make: Target 'all' not remade because of errors.
</pre>
<p>The likely culprit here is that g++ is not on your Path.<br>
<p>The Error 255 is produced by make as a result of its command shell not being able to find a command for a particular rule.<br>
Messages from the standard error stream (the lines saying Error 255) and standard output stream (all the other lines) are merged in the Console view here.</p>
<p><strong>Q5. What's with the -k flag?</strong></p>
<p>The -k flag tells make to continue making other independent rules even when one rule fails.
This is helpful for build large projects.</p>
<p>You can remove the -k flag by turning on Project Properties > C/C++ Make Project > Make Builder > Stop on first build error</p>
<p><strong>Q6. My Console view looks like:</strong></p>
<pre>
mingw32-make clean all
process_begin: CreateProcess((null), rm -f Test1.o Test2.o Main.o test_me.exe, ...) failed.
make (e=2): The system cannot find the file specified.
mingw32-make: *** [clean] Error 2
rm -f Test1.o Test2.o Main.o test_me.exe
</pre>
<p>This means that mingw32-make was unable to find the utility "rm". Unfortunately, MinGW does not come with "rm". To correct this, replace the clean rule in your Makefile with:</p>
<p><pre>
clean :
-del $(REBUILDABLES)
echo Clean done
</pre></p>
<p>The leading minus sign tells make to consider the clean rule to be successful even if the del command returns failure. This may be acceptable since the del command will fail if the specified files to be deleted do not exist yet (or anymore).</p>
<p><img src="../images/ng00_04a.gif" ALT="IBM Copyright Statement" ></p>
</div>
</body>
</html>

40
debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_open_declarations.htm
View file

@ -1,40 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Open Declaration</title>
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<div role="main">
<h1>Open Declaration</h1>
<p>You can select an element name in your code and quickly navigate to its declaration.</p>
<img src="../images/openDeclaration.png" alt="Editor View showing Open Declaration option">
<p>Open declaration will attempt to navigate to the exact definition of the selected element if the selected element is a reference or a declaration.
Otherwise, it will attempt to navigate to a declaration of the selected element.
Open declaration requires your file to have the proper include paths set up to the declaration.
If for any reason open declaration cannot find the declaration, it will display the following message in the status line:</p>
<img src="../images/open_declaration_error.png" alt="No declaration was found message.">
<p>For more information see <a href="../tasks/cdt_t_sd.htm">Setting up include paths and macros for C/C++ indexer</a>.</p>
<p><img src="../images/ngconcepts.gif" ALT="Related concepts" width="143" height="21"> <br>
<a href="cdt_c_projects.htm">C/C++ Projects</a><br>
<a href="cdt_c_search.htm">C/C++ search</a></p>
<p><img src="../images/ngtasks.gif" ALT="Related tasks" width="143" height="21"> <br>
<a href="../tasks/cdt_t_sd.htm">Setting up include paths and macros for C/C++ indexer</a><br>
<a href="../tasks/cdt_t_open_declarations.htm">Navigate to a C or C++ element's declaration</a><br>
<a href="../tasks/cdt_t_search.htm">Searching for C/C++ elements</a></p>
<p><img src="../images/ng00_07.gif" ALT="IBM Copyright Statement" width="324" height="14"> </p>
</div>
</body>
</html>

131
debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_outlineview.htm
View file

@ -1,131 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Outline view</title>
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<div role="main">
<h1>Outline view </h1>
<p>The Outline view displays an outline of a structured C/C++ file that is currently
open in the editor area, by listing the structural elements. </p>
<img src="../images/outlineView.png" alt="Editor View highlighting corresponding element in the Outline View"></li>
<p>The Outline view shows the following elements in the source file in the order
in which they occur:</p>
<ul>
<li>Class</li>
<li>Namespace</li>
<li>Include</li>
<li>Enum</li>
<li>Enumerator</li>
<li>Field private</li>
<li>Field protected</li>
<li>Field public</li>
<li>Include</li>
<li>Method private</li>
<li>Method protected</li>
<li>Method public</li>
<li>Struct</li>
<li>Typedef</li>
<li>Union</li>
<li>Variable</li>
<li>Function</li>
<li>Macro Definition</li>
</ul>
<p>You can also sort the list
alphabetically. When you select an element in the Outline view, the C/C++
editor highlights both the selected item and the marker bar (left margin). For example, to move
to the start of main() in the C/C++ editor, click <samp>main()</samp> in the Outline
view.</p>
<p>For more information about the marker bar, see <strong>Workbench User Guide &gt; Reference &gt; User interface
information &gt; Views and editors &gt; Editor area</strong>.</p>
<h2>Filtering the Outline View</h2>
<p>You can filter the Outline view by choosing to display or hide the following
items:</p>
<ul>
<li>Fields</li>
<li>Static members</li>
<li>Non-public members</li>
</ul>
<p>You can select an element in the Outline view, and perform the following actions:</p>
<ul>
<li>Open the C/C++ Search window box. The Search string box is populated and
the element type is selected.</li>
<li>Complete a text-based search, of a workspace or a specified working set for the
selected element.</li>
<li>Open a selected .h file in the editor.</li>
<li>Rename Refactor</li>
</ul>
<h2>Icons</h2>
<p><table border="1" cellpadding="5" cellspacing="0" style="border-collapse: collapse" bordercolor="#DDDDDD" width="34%">
<tr>
<th style="width:19%" id="icon"><strong>Icon</strong></th>
<th style="width:81%" id="description"><strong>Description</strong></th>
</tr>
<tr>
<td style="text-align:center;" headers="icon"><img src="../images/icon_collapse_all.png" alt="Collapse All Icon" width="16" height="16"></td>
<td headers="description">Collapse All</td>
</tr>
<tr>
<td style="text-align:center;" headers="icon"><img src="../images/alphab_sort_co.gif" alt="Sort items alphabetically Icon" width="16" height="16"></td>
<td headers="description">Sort items alphabetically</td>
</tr>
<tr>
<td style="text-align:center;" headers="icon"><img src="../images/fields_co.gif" alt="Hide Fields Icon" width="16" height="16"></td>
<td headers="description">Hide Fields</td>
</tr>
<tr>
<td style="text-align:center;" headers="icon"><img src="../images/static_co.gif" alt="Hide Static Members Icon" width="16" height="16"></td>
<td headers="description">Hide Static Members </td>
</tr>
<tr>
<td style="text-align:center;" headers="icon"><img src="../images/public_co.gif" alt="Hide Non-Public Members Icon" width="16" height="16"></td>
<td headers="description">Hide Non-Public Members </td>
</tr>
<tr>
<td style="text-align:center;" headers="icon"><img src="../images/icon_hide_inactive_includes.png" alt="Hide Inactive Elements Icon" width="16" height="16"></td>
<td headers="description">Hide Inactive Elements </td>
</tr>
</table></p>
<p>For more information about the Eclipse workbench, see <strong>Workbench User Guide &gt; Tasks &gt; Upgrading Eclipse</strong>.</p>
<p>For more information about Working sets, see <strong>Workbench User Guide &gt; Concepts &gt; Working sets</strong>.</p>
</ul>
<p><img src="../images/ngconcepts.gif" ALT="Related concepts" width="143" height="21">
<br>
<a href="cdt_c_comments.htm">Comments</a><br>
<a href="cdt_c_content_assist.htm">Content Assist and code completion</a><br>
<a href="cdt_c_search.htm">C/C++ search</a><br>
<a href="cdt_c_open_declarations.htm">Open Declaration</a><br>
&nbsp;</p>
<p><img src="../images/ngtasks.gif" ALT="Related tasks" width="143" height="21">
<br>
<a href="../tasks/cdt_t_show_proj_files.htm">Displaying C/C++ file components in the
Project Explorer view</a><br>
<a href="../tasks/cdt_t_search.htm">Searching for C/C++ elements</a></p>
<p><img src="../images/ngref.gif" ALT="Related reference" width="143" height="21">
<br>
<a href="../reference/cdt_u_outline_view.htm">Outline view</a><br>
&nbsp;</p>
<img src="../images/ng00_07.gif" ALT="IBM Copyright Statement" >
</div>
</body>
</html>

92
debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_over_cdt.htm
View file

@ -1,92 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>CDT overview</title>
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<div role="main">
<h1>CDT Overview</h1>
<p>The C/C++ Development Toolkit (CDT) is a set of Eclipse plug-ins that provide
C and C++ extensions to the Eclipse workbench. For more information about
Eclipse, see <strong>Workbench User Guide &gt; Concepts &gt; Workbench</strong>.</p>
<p>The full CDT provides a C/C++ IDE that simplifies many of the same tools that you can use from the command line. The CDT can also communicate with many external utilities and interpret their responses, for example:
<ul>
<li>Build (such as make).</li>
<li>Compile (such as gcc). For more information, see <a href="https://gcc.gnu.org">https://gcc.gnu.org</a>.</li>
<li>Debug (such as gdb). For more information, see <a href="https://sources.redhat.com/gdb/">https://sources.redhat.com/gdb/</a>.</li>
</ul>
<strong>Note: </strong> while make, gcc and gdb are the examples used in the documentation, virtually any similar set of tools or utilities could be used.</p>
<p>The Stand-alone Debugger application is built from various Eclipse plug-ins from the CDT pertaining to Debug and Edit. Plug-ins associated
with Build and Compile are not included. Though it is possible to edit files within the Stand-alone Debugger, any changes
will require a rebuild which will have to be performed outside of the Debugger. If you want a full C/C++ IDE, then it is suggested to use the full CDT
instead which incorporates the C/C++ Debugger within it.</p>
<!--
<p>The Stand-alone Debugger opens in the Debug perspective of the Eclipse workbench. The
C/C++ perspective consists of an editor and the following
views:</p>
<dl>
<dt>Project Explorer</dt><dd>Shows all of the file system's files under your workspace directory.</dd>
<dt>Console</dt><dd>Displays your program's output, as well as the output from your build and external tool chain.</dd>
<dt>Editor</dt><dd>The C/C++ editor view provides specialized features for editing C/C++ related files.</dd>
<dt>Make Targets</dt><dd>Enables you to select the make targets you want to build in your workspace.</dd>
<dt>Outline</dt><dd>Displays the structure of the file currently open in an editor.</dd>
<dt>Problems View</dt><dd>If you encounter any errors during a build they will be displayed in the Problems view.</dd>
<dt>Properties</dt><dd>Shows the attributes of the item currently selected in a view or an editor.</dd>
<dt>Search</dt><dd>Shows the results of searches for files or text.</dd>
<dt>Tasks</dt> <dd>Lists tasks that you want to keep track of, either as a schedule of things to do or a history of things that have been done.</dd>
</dl>
<p>For more information, see <strong>Workbench User Guide &gt; Concepts &gt; Perspectives</strong>.</p>
<h2>CDT updates</h2>
<p>The <strong>Install/Update</strong> wizard provides information about your current Eclipse installation and provides the framework to manage your updates.
For more information, see <strong>Workbench User Guide &gt; Tasks &gt; Updating and installing software</strong>.</p>
<p>To view a list of the updates available for the toolsets that you
installed, click <strong>Help &gt; Check for Updates</strong>.</p>
-->
<h3>Additional information</h3>
<p>For more information on the Eclipse CDT project,
refer to <a href="https://www.eclipse.org/cdt/">https://www.eclipse.org/cdt/</a>:
</p>
<ul>
<li><a href="https://github.com/eclipse-cdt/cdt/discussions" target="_top">Eclipse CDT Discussions</a>:
The place to ask questions about how to use the CDT.</li>
<li><a href="https://github.com/eclipse-cdt/cdt/tree/main/FAQ">User FAQ</a>:
Provides answers to the most common questions about using the CDT.</li>
<li><a href="https://github.com/eclipse-cdt/cdt">CDT on GitHub</a>:
This is the main source for information around CDT.</li>
</ul>
<h3>License</h3>
<p>The CDT is an open source project and is licensed under the <a href="https://www.eclipse.org/legal/epl-2.0/">Eclipse Public License</a>.
<!--
<p>
<img src="../images/ngconcepts.gif" ALT="Related concepts" width="143" height="21">
<br>
<a href="../getting_started/cdt_w_existing_code.htm">Working with existing code</a><br>
<a href="cdt_c_whatsnew.htm">What's new</a></p>
-->
<p><img src="../images/ngref.gif" ALT="Related reference" width="143" height="21">
<br>
<a href="../reference/cdt_o_views.htm">Views</a></p>
<img src="../images/ng00_07.gif" ALT="IBM Copyright Statement" >
</div>
</body>
</html>

46
debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_over_dbg.htm
View file

@ -1,46 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
<meta name="ProgId" content="FrontPage.Editor.Document">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Debug overview</title>
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<div role="main">
<h1>Debug overview</h1>
<p>The debugger lets you see what's going on &quot;inside&quot; a program while it
executes.</p>
<p>In order to debug your application, you must use executables compiled for
debugging. These executables contain additional debug information that lets the
debugger make direct associations between the source code and the binaries
generated from that original source.</p>
<p>The Stand-alone debugger uses GDB as the underlying debug engine. It translates each
user interface action into a sequence of GDB commands and processes the output from GDB to
display the current state of the program being debugged. </p>
<p><strong>Tip:</strong> Editing the source after compiling causes the line numbering to be out of
step because the debug information is tied directly to the source. Similarly,
debugging optimized binaries can also cause unexpected jumps in the execution
trace.</p>
<p><img src="../images/ngconcepts.gif" ALT="Related concepts" width="143" height="21">
<br>
<a href="cdt_c_over_cdt.htm">Overview of the CDT</a><br>
<a href="cdt_c_dbg_info.htm">Debug information</a></p>
<p><img src="../images/ngtasks.gif" ALT="Related tasks" width="143" height="21">
<br>
<a href="../tasks/cdt_o_debug.htm">Debugging</a><br>
&nbsp;</p>
<p><img src="../images/ngref.gif" ALT="Related reference" width="143" height="21">
<br>
<a href="../reference/cdt_o_run_dbg_pages.htm">Run and Debug dialog box</a></p><p>
<img src="../images/ng00_04a.gif" ALT="IBM Copyright Statement" > </p>
</div>
</body>
</html>

76
debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_perspectives.htm
View file

@ -1,76 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>Perspectives available to C/C++ developers</title>
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<div role="main">
<h1>Perspective</h1>
<p>A perspective is a layout of <a href="cdt_c_views.htm">views</a> (development tools) in the Workbench window.
Each type of perspective is a combination of views, menus, and toolbars that enable you to perform a particular task.
In the Stand-alone Debugger, you only have the choice of the <strong>Debug</strong> perspective which has views that
enable you to debug programs. When ever you use the Stand-alone Debugger, you will be placed into the <strong>Debug</strong>
perspective.
</p>
<div class="note">
<strong>Selecting / Opening Views:</strong>
<ul>
<li>You can add views to the perspective. From the menu bar choose <strong>Window &gt; Show View</strong> and open a category then select a new view from the <strong>Show View</strong> dialog.</li>
<li>To reset the <strong>Debug</strong> perspective to its original layout, from the menu bar choose <strong>Window &gt; Reset Perspective</strong>.</li>
</ul>
</div>
<p>The C/C++ development tools contribute the following perspectives to the workbench:
</p>
<p>There a several additional views that may be useful during a debug session. You can add them by clicking <strong>Window &gt; Show View &gt; C/C++</strong> to show them in the C/C++ perspective.</p>
<h2>Debug perspective views</h2>
<p>The Debug perspective is tuned for debugging your C/C++ program.
By default it includes an editor area and the following views:
</p>
<ul>
<li><a href="../reference/cdt_u_dbg_view.htm">Debug</a></li>
<li>Variables</li>
<li>Breakpoints</li>
<li><a href="../reference/cdt_u_outline_view.htm">Outline</a></li>
<li><a href="../reference/cdt_u_console_view.htm">Console</a></li>
<li>Tasks</li>
<li><a href="../reference/cdt_u_problems_view.htm">Problems</a></li>
<li><a href="../reference/cdt_u_view_executables.htm">Executables</a></li>
</ul>
<p>There a several additional views that may be useful during a debug session. You can add them by clicking <strong>Window &gt; Show View &gt; Debug</strong> to show them in the Debug perspective.</p>
<h2>Additional C/C++ views</h2>
<p>There are some additional C/C++ views that are provided that may be accessed using <strong>Window &gt; Show View &gt; C/C++</strong>.
These will normally not be needed for debugging but may be helpful if there are problems and the user has an understanding
of the full CDT IDE. The additional views are:
</p>
<ul>
<li><a href="../reference/cdt_u_cproj_view.htm">C/C++ Projects</a></li>
<li>C/C++ Index view</li>
<li>Call Hierarchy</li>
<li>Include Browser</li>
<li>Type Hierarchy</li>
</ul>
<p><img src="../images/ngref.gif" ALT="Related reference" width="143" height="21">
<br>
<a href="../reference/cdt_o_views.htm">C/C++ Views and Editors</a></p>
<p>
<img src="../images/rh03_04.gif" ALT="Red Hat Copyright Statement"><br>
<img src="../images/ng00_04a.gif" ALT=" IBM Copyright Statement" >
</p>
</div>
</body>
</html>

66
debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_proj_file_views.htm
View file

@ -1,66 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Project file views</title>
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<div role="main">
<h1>Project file views</h1>
<p>Projects files and elements are displayed in the C/C++ Projects view and in the ProjectExplorer view.</p>
<h2>C/C++ Projects view</h2>
<p>Displays, in a tree structure, only elements relevant to C and C++ projects. In this view you can do the following:
<ul>
<li>Browse the elements of C/C++ source files</li>
<!-- <li>Build Targets</li> -->
<!-- <li>Create new projects, classes, files, or folders</li> -->
<li>Import or Export files and projects</li>
<li>Manage existing files (cut, paste, delete, move or rename)</li>
<li>Open files in the editor view</li>
<li>Open projects in a new window</li>
<!-- <li>Refactor</li> -->
<li>Restore deleted files from local history</li>
<li>Search</li>
</ul>
Files that you select in the C/C++ Projects view affect the information that is displayed in other views.</p>
<img src="../images/view_projects.png" alt="C/C++ Projects View">
<h2>Project Explorer view</h2>
<p>The Project Explorer view provides a hierarchical view of all the resources in the workbench, not just your C/C++ resources.
From this view, you can open files for editing or select resources for operations such as exporting. </p>
<p>Right-click any resource in the Project Explorer view to open a pop-up menu from which you can perform operations such as
copy, move, create new resources, compare resources, or perform team operations. For a description of what each menu
item does, select an item and press F1. </p>
<p>The Project Explorer view is provided by the Eclipse Platform. <!-- See the <a href="PLUGINS_ROOT/org.eclipse.platform.doc.user/reference/ref-27.htm">Workbench User Guide</a> for more information.</p> -->
<!-- <p><img src="../images/ngconcepts.gif" ALT="Related concepts" width="143" height="21">
<br>
<a href="cdt_c_projects.htm">CDT Projects</a><br>
<a href="../getting_started/cdt_w_existing_code.htm">Working with existing code</a></p>
<p><img src="../images/ngtasks.gif" ALT="Related tasks" width="143" height="21">
<br>
<a href="../tasks/cdt_t_proj_new.htm">Creating a project</a><br>
<a href="../tasks/cdt_t_proj_new_with_template.htm">Creating a project via a project template</a><br>
<a href="../tasks/cdt_o_proj_files.htm">Working with C/C++ project files</a></p>
<p><img src="../images/ngref.gif" ALT="Related reference" width="143" height="21">
<br>
-->
<a href="../reference/cdt_u_icons.htm">C/C++ perspective icons</a></p>
<p>
<img src="../images/ng00_07.gif" ALT="IBM Corporation Statement" ></p>
</div>
</body>
</html>

42
debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_projects.htm
View file

@ -1,42 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>CDT projects</title>
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<div role="main">
<h1>C/C++ projects</h1>
<p>Normally, before you can work with plug-ins provided by the CDT, you must create an Eclipse project to store your
source code, makefiles, binaries, and related files. However, when you use the Stand-alone Debugger, a project is created
for your executable automatically (usually the <strong>Executables</strong> project if only dealing with one executable).
The project created on your behalf just contains the executable and links to the source files specified in the debug
info. In most cases, you do not need to know about the project to debug, but if you wish to see the various files used
and browse them directly with the editor, you can find the project in the C/C++ Projects view. While you are allowed to import
files into the C/C++ project, this action is normally used for adding files to a project that can build. Since the Stand-alone
Debugger does not contain CDT (C/C++ Developer Tools) build capability, adding files does nothing to aid in debugging and can
confuse the indexer if the source has errors in it.</p>
<p><img src="../images/ngconcepts.gif" ALT="Related concepts" width="143" height="21">
<br>
<a href="cdt_c_proj_file_views.htm">Project file views</a><br>
<p><img src="../images/ngtasks.gif" ALT="Related tasks" width="143" height="21">
<br>
<a href="../tasks/cdt_o_proj_files.htm">Working with C/C++ project files</a><br>
</p>
<p><img src="../images/ngref.gif" ALT="Related reference" width="143" height="21">
<br>
<a href="../reference/cdt_o_proj_prop_pages.htm">Project properties</a><br>
<a href="../reference/cdt_o_views.htm">Views</a></p>
<img src="../images/ng00_04a.gif" ALT="IBM Copyright Statement" >
</div>
</body>
</html>

108
debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_scanner_discovery.htm
View file

@ -1,108 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<meta name="copyright" content="Copyright (c) Andrew Gvozdev and others 2013,2013. This page is made available under license. For full details, see the LEGAL section in the documentation that contains this page.">
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Scanner Discovery</title>
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<div>
<h1>Scanner Discovery</h1>
<p>
<h2>General</h2>
<strong>Scanner Discovery</strong> (sometimes called <strong>Autodiscovery</strong>) is a method of finding include paths and predefined preprocessor macros which the compiler uses during compilation of the code.
</p>
<p>
Even a simplest C/C++ program just printing "Hello World" needs to include system headers. Consider:
</p>
<pre>
#include &lt;stdio.h&gt;
#include &lt;stdlib.h&gt;
int main(void) {
puts("!!!Hello World!!!");
return EXIT_SUCCESS;
}
</pre>
<p>
Indexer needs to be able to find headers <span class="typewriter">stdio.h</span> and <span class="typewriter">stdlib.h</span> and parse them to provide accurate index.
In this example, the headers define prototype of function <span class="typewriter">puts</span> and macro <span class="typewriter">EXIT_SUCCESS</span>.
</p>
<p>
The Stand-alone Debugger will try to discover include paths and preprocessor symbols automatically.
There are 2 main ways to discover those:
</p>
<ol>
<li><strong>Built-in</strong> Settings.
The debugger will try to detect built-in compiler symbols and include paths running the compiler with special options and parse the output of this special run.
Most compilers provide such an option to print built-in include paths and symbols. Built-in settings are implied and do not get passed to the compiler during regular compilation.
</li>
<li><strong>Build Output Parser (BOP)</strong>.
Another method that the debugger employs is to analyze build output you provide to its Build Output Parser.
Often, include paths are supplied to the compiler with <span class="typewriter">-I</span> options, and macros with <span class="typewriter">-D</span> options
and BOP will try to find those in the output.
That method relies on verbose build output of your build where all these options are actually printed by make. To
specify build output either use the <strong>-b</strong> command-line option or else specify the location of the
build log when using the <strong>File &gt; New Executable...</strong> dialog.
</li>
</ol>
<p>
The debugger uses <strong>Language Settings Providers</strong> to discover the settings (starting with version CDT 8.1). Typically Language settings Providers are specialized.
One will provide built-in compiler settings and another one settings detected by Build output Parser.
</p>
<p>
The setting entries found by Scanner Discovery can be inspected in project properties on "Preprocessor Include Paths, Macros etc." page.
Each Language Settings Provider can be expanded to show the entries it discovered.
</p>
<p>
<img src="../images/scanner_discovery/sd_prop_entries.png" alt="Preprocessor Include Paths and Macros Entries">
</p>
<p>
If information retrieved by auto-discovery is insufficient a user can enter additional include paths and macros manually under "User Settings Entries".
</p>
<h2>Console View</h2>
<p>
The output of built-in compiler specs detectors can be inspected to troubleshoot problems running the command.
To do so, enable checkbox "Allocate console in the Console View".
</p>
<p>
<img src="../images/scanner_discovery/sd_specs_detector_options.png" alt="Spec Detectors Properties"></img>
</p>
<p>
When checkbox "Allocate console in the Console View" is enabled, output of each run of the provider will be directed to a special console in the Console View.
</p>
<p>
<img src="../images/scanner_discovery/sd_console_view.png" alt="Console View"></img>
</p>
<p><img src="../images/ngconcepts.gif" alt="Related concepts" width="143" height="21"><br>
<a href="../concepts/cdt_c_indexer.htm">C/C++ Indexer</a><br>
</p>
<p><img src="../images/ngtasks.gif" alt="Related tasks" width="143" height="21"><br>
<a href="../tasks/cdt_t_sd.htm">Setting up include paths and macros for C/C++ indexer</a><br>
</p>
<p><img src="../images/ngref.gif" alt="Related reference" width="143" height="21"><br>
<a href="../reference/cdt_u_pref_build_scanner_discovery.htm">C/C++ Preferences: Scanner Discovery</a><br>
<a href="../reference/cdt_u_prop_general_scanner_discovery.htm">C/C++ Project properties: Preprocessor Include Paths, Macros, etc.</a><br>
</p>
</div>
</body>
</html>

275
debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_search.htm
View file

@ -1,275 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>C/C++ search</title>
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<div role="main">
<h1>C/C++ search</h1>
<p>You can conduct a fully or partially qualified name search. Further
qualifying a search increases the accuracy and relevance of search results. The
sections below provide guidance on how to control the scope of your search
through the use of search delimiters, correct syntax, and wildcards.</p>
<p>You can search for:<br>
<ul>
<li>language constructs within:
<ul>
<li>projects in your workspace</li>
<li>selected resources from various views</li>
<li>working sets</li>
</ul></li>
<li>a working set for references to particular elements</li>
<li>declarations of particular elements</li>
<li>definitions of particular elements</li>
<li>references of particular elements</li>
</ul>
</p>
For information on working sets, see <strong>Workbench User Guide &gt; Concepts &gt; Workbench &gt; Working sets</strong><br>
<h2>What you can search for</h2>
<p>The table below lists the element types that you can search for and special
considerations to note when searching for a given element type. You can search
for some or all of the element types matching a search string that you
specify. If you choose to search for matching elements, all types, macros, and typdefs are included in the search.</p>
<table border="2" cellpadding="2" cellspacing="0" style="border-collapse: collapse" bordercolor="#AAA" width="60%">
<tr>
<th style="width:25%; text-align:left" id="element"><strong>Element</strong></th>
<th style="width:75%; text-align:left" id="note"><strong>Note</strong></th>
</tr>
<tr>
<td style="width:25%" headers="element" valign="top">&nbsp;Class/Struct</td>
<td style="width:75%" headers="note">Searches for classes and structs.<p>You can further qualify
the search by specifying &quot;class&quot; or &quot;struct&quot; in front of the name
that you are
searching for. Specifying &quot;class&quot; or &quot;struct&quot; also allows you to
search for anonymous classes and structures.</td>
</tr>
<tr>
<td style="width:25%" headers="element" valign="top">&nbsp;Function</td>
<td style="width:75%" headers="note">Searches for global functions or functions in a namespace
(functions that are not members of a class, struct, or union).<p>You can
specify parameters to further qualify your search. When specifying a
parameter list, everything between the parentheses should be valid C/C++
syntax.</p>
<p>Do not specify the return type of the function.</td>
</tr>
<tr>
<td style="width:25%" headers="element" valign="top">&nbsp;Variable</td>
<td style="width:75%" headers="note">Searches for variables that are not members of a class,
struct, or union.</td>
</tr>
<tr>
<td style="width:25%" headers="element" valign="top">&nbsp;Union</td>
<td style="width:75%" headers="note">Searches for unions.<p>Anonymous unions can be searched for by
specifying &quot;union&quot; as the search pattern.</td>
</tr>
<tr>
<td style="width:25%" headers="element" valign="top">&nbsp;Method</td>
<td style="width:75%" headers="note">Searches for methods that are members of a class, struct, or
union.<p>Searching for methods also finds constructors and destructors. See
above note for functions.</td>
</tr>
<tr>
<td style="width:25%" headers="element" valign="top">&nbsp;Field </td>
<td style="width:75%" headers="note">Searches for fields that are members of a class, struct, or
union.
</tr>
<tr>
<td style="width:25%" headers="element" valign="top">&nbsp;Enumeration</td>
<td style="width:75%" headers="note">Searches for enumerations.</td>
</tr>
<tr>
<td style="width:25%" headers="element" valign="top">&nbsp;Enumerator</td>
<td style="width:75%" headers="note">Searches for enumerators.</td>
</tr>
<tr>
<td style="width:25%" headers="element" valign="top">&nbsp;Namespace</td>
<td style="width:75%" headers="note">Searches for namespaces.</td>
</tr>
</table>
<h2>How you can limit your search</h2>
<p>You can limit your search to one or all of the following:</p>
<ul>
<li>Declarations</li>
<li>References</li>
<li>Definitions (for functions, methods, variables and fields)</li>
</ul>
<p>You can control the scope of the search by specifying which of the following
is to be searched:</p>
<ul>
<li>Workspace</li>
<li>Working Set</li>
<li>Selected Resources</li>
</ul>
<h2>Wildcard characters</h2>
<p>You can use wildcard characters to further refine your search.</p>
<table border="2" cellpadding="2" cellspacing="0" style="border-collapse: collapse" bordercolor="#AAA" width="60%">
<tr>
<th style="width:30%; text-align:left" id="char" valign="top"><strong>Use this wildcard character</strong></th>
<th style="width:70%; text-align:left" id="search"><strong>To search for this</strong></th>
</tr>
<tr>
<td style="width:30%" headers="char" valign="top">&nbsp;<samp>*</samp></td>
<td style="width:70%" headers="search">Any string<p><strong>Tip:<br>
</strong> Use the character sequence <samp>\*</samp> to search for
operators that begin with *. See syntax examples in the table below.</td>
</tr>
<tr>
<td style="width:30%" headers="char" valign="top">&nbsp;<samp>?</samp></td>
<td style="width:70%" headers="search">A single character</td>
</tr>
<tr>
<td style="width:30%" headers="char" valign="top">&nbsp;<samp>::</samp></td>
<td style="width:70%" headers="search">Nested elements</td>
</tr>
</table>
<!-- no support for function parameters
<p><strong>Tip: </strong>Do not use wild cards between the brackets of a function or
method pattern. For example, the search
string <samp>f( * )</samp> is an invalid search that results in a search for any function <samp>f</samp>
because
the asterisk is interpreted as a pointer rather than a wild card.</p>
-->
<h2>Syntax examples</h2>
<p>The table below provides syntax examples and an explanation for each example
to help you conduct an effective search.</p>
<table border="2" cellpadding="2" cellspacing="0" style="border-collapse: collapse" bordercolor="#AAA" width="60%">
<tr>
<th style="width:30%; text-align:left" id="syntax"><strong>Syntax</strong></th>
<th style="width:70%; text-align:left" id="search2"><strong>Searches for this</strong></th>
</tr>
<tr>
<td style="width:30%" headers="syntax">&nbsp; <samp>::*::*::A</samp></td>
<td style="width:70%" headers="search2">A nested element two levels deep</td>
</tr>
<tr>
<td style="width:30%" headers="syntax">&nbsp; <samp>::*::*::A?</samp></td>
<td style="width:70%" headers="search2">Any two-letter name that begins with A and is two levels
deep</td>
</tr>
<tr>
<td style="width:30%" headers="syntax">&nbsp; <samp>::A</samp> </td>
<td style="width:70%" headers="search2">Searches for A not nested in anything</td>
</tr>
<!-- no support for function parameters
<tr>
<td style="width:30%" headers="syntax">&nbsp; <samp>*()</samp></td>
<td style="width:70%" headers="search2">Any function taking no parameters</td>
</tr>
<tr>
<td style="width:30%" headers="syntax">&nbsp;&nbsp;<samp>*( A * )</samp> </td>
<td style="width:70%" headers="search2">Any function taking 1 parameter that is a pointer to type
A</td>
</tr>
<tr>
<td style="width:30%" headers="syntax">&nbsp;&nbsp;<samp>f( int * )</samp></td>
<td style="width:60%" headers="search2">Will search for function f taking 1 parameter that is an
int *</td>
</tr>
<tr>
<td style="width:30%" headers="syntax">&nbsp;&nbsp;<samp>f( const char [
], A &amp; )</samp></td>
<td style="width:60%" headers="search2">Will search for a function f, taking 2 parameters; one is a
const char array, the other is a reference to type A</td>
</tr>
-->
<tr>
<td style="width:30%" headers="syntax">&nbsp;<samp>operator \*</samp></td>
<td style="width:60%" headers="search2">Finds only operator *</td>
</tr>
<tr>
<td style="width:30%" headers="syntax">&nbsp;<samp>operator \*=</samp></td>
<td style="width:60%" headers="search2">Finds only operator *=</td>
</tr>
<tr>
<td style="width:30%" headers="syntax">&nbsp;<samp>operator *</samp></td>
<td style="width:60%" headers="search2">Finds all operators</td>
</tr>
<tr>
<td style="width:30%" headers="syntax">&nbsp;<samp>class</samp></td>
<td style="width:60%" headers="search2">Searches for anonymous classes</td>
</tr>
<tr>
<td style="width:30%" headers="syntax"> &nbsp;<samp>struct</samp></td>
<td style="width:60%" headers="search2">Searches for anonymous structs</td>
</tr>
<tr>
<td style="width:30%" headers="syntax"> &nbsp;<samp>union</samp></td>
<td style="width:60%" headers="search2">Searches for anonymous unions</td>
</tr>
</table>
<h2>Search results</h2>
<p>Search results are displayed in the Search view. You can sort your search by Name, Parent Name and Path. You can also repeat
your last search.</p>
<h2>Search Concepts</h2>
<h3>Declarations</h3>
<p>According to the ANSI C++ Spec, a declaration is a statement that <Q>introduces a name into a translation unit or re-declares a name that has been previously introduced by a previous declaration</Q>.</p>
<p>All C/C++ search elements can be searched for declarations.</p>
<h3>Definitions</h3>
<p>Most declarations are also definitions; in other words, they also define the entity for they declare the name for. However there are some elements that can have separate definitions from their declarations.</p>
<p>For C/C++ search the following elements can be searched for definitions:
<ul>
<li>Functions/Methods - the definition is where the code implementation resides</li>
<li>Variable:
<ol>
<li>Extern - the definition is where the variable is initialized</li>
<li>Non extern - the definition of a variable is where it is declared </li>
</ol></li>
<li>Field:
<ol>
<li>Static fields - the definition of a static field is where it gets initialized</li>
<li>Non static fields - the definition corresponds to the fields declaration</li>
</ol></li>
<li>Namespace - the definition of a namespace is the same as its declaration</li>
</ul></p>
<h3>References</h3>
<p>By selecting references, C/C++ search will return all of the places the selected element is used.</p>
<h3>All Occurrences</h3>
<p>Selecting 'All Occurrences' in the Limit To section will result in a search for declarations, definitions (if applicable) and references for whatever element or elements have been selected.</p>
<h3>Any Element</h3>
<p>Selecting 'Any Element' in the Search For section will result in a search for all of the listed elements plus macros and typedefs.</p>
<p>For more information, see:<ul>
<li> <strong>Workbench User Guide &gt; Concepts &gt; Views &gt; Search view</strong></li>
<li> <strong>Workbench User Guide &gt; Tasks &gt; Navigating and finding resources</strong></li>
</ul>
<p><img src="../images/ngconcepts.gif" ALT="Related concepts" width="143" height="21"><br>
<a href="../concepts/cdt_c_indexer.htm">C/C++ Indexer</a><br>
<a href="cdt_c_projects.htm">C/C++ Projects</a><br>
<a href="cdt_c_open_declarations.htm">Open Declaration</a><br>
</p>
<p><img src="../images/ngtasks.gif" ALT="Related tasks" width="143" height="21">
<br>
<a href="../tasks/cdt_t_search.htm">Searching for C/C++ elements</a><br>
<a href="../tasks/cdt_t_open_declarations.htm">Navigating to C/C++ declarations</a><br>
</p>
<p><img src="../images/ngref.gif" ALT="Related reference" width="143" height="21"> <br>
<a href="../reference/cdt_u_search.htm">C/C++ search page, Search dialog box</a><br>
<a href="../reference/cdt_u_icons.htm">C/C++ perspective icons</a></p><p>
<img src="../images/ng00_07.gif" ALT="IBM Copyright Statement" ></p>
</div>
</body>
</html>

47
debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_standalone_intro.htm
View file

@ -1,47 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Introduction</title>
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<div role="main">
<h1>Introduction</h1>
<p>The Stand-alone Debugger is an Eclipse application which packages the
Eclipse plug-ins from the CDT (C/C++ Development Tools) project into an
application that can be started from a command-line script. The debugger
removes some of the plug-ins that would be found in the full CDT set that
are related to building and project set-up. This simplifies the UI for
the end-user who is only interested in debugging and is not interested in
using Eclipse to build the application itself.</p>
<p>In addition, the Stand-alone debugger helps to simplify debugging in that
it hides Eclipse-specific concepts such as the Eclipse project and launch
configuration. While these concepts are hidden, they still are used underneath
and an experienced Eclipse user can still access them. Subsequent documentation
here will attempt to point out where such concepts are being automated by the
Stand-alone Debugger and how they can still be accessed.</p>
<p><img style="border: 0px solid ; width: 143px; height: 21px;"
src="../images/ngconcepts.gif" alt="Related concepts"> <br>
<a href="../concepts/cdt_c_over_cdt.htm">CDT Overview</a><br>
<a href="../concepts/cdt_c_projects.htm">C/C++ Projects</a><br>
<a href="../concepts/cdt_c_perspectives.htm">C/C++ Perspectives</a><br>
<a href="../concepts/cdt_c_indexer.htm">C/C++ Indexer</a><br>
<a href="../concepts/cdt_c_search.htm">C/C++ Search</a></p>
<p><img src="../images/ngref.gif" ALT="Related reference" width="143" height="21">
<br>
<a href="../reference/cdt_o_views.htm">Views</a><br>
<p><img src="../images/ngtasks.gif" ALT="Related tasks" width="143" height="21">
<br>
<a href="../tasks/cdt_t_standalone_startup.htm">Starting the debugger</a><br>
<img src="../images/intl_07.gif" ALT="Intel Copyright Statement" >
</div>
</body>
</html>

66
debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_templates.htm
View file

@ -1,66 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Templates</title>
<link rel="stylesheet" type="text/css" href="../help.css">
<script type="text/javascript"
src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
</head>
<body>
<div role="main">
<h1>Templates</h1>
<p>
Templates are sections of code that occur frequently enough that you
would like to be able to insert them with a few keystrokes. This
function is known as <strong>Content Assist</strong>; the sections of
code that are inserted are known as <strong>templates</strong>.
</p>
<p>
To insert an existing Content Assist template into a file, such as
one for an <strong>if</strong> statement, type the initial character
("<span class="typewriter">i</span>" in this case), then press <strong>Ctrl+Space</strong>.
The templates that begin with that character appear. Double-click on
a template to insert it into a file.
</p>
<p>
You can edit the existing Content Assist templates or create new
ones using the <img src="../images/command_link.png" alt=""> <a
class="command-link"
href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.cdt.ui.preferences.TemplatePreferencePage)")'>C/C++
&gt; Editor &gt; Templates</a> preference pane.
</p>
<p>
<img src="../images/ngconcepts.gif" ALT="Related concepts"
width="143" height="21"> <br> <a
href="cdt_c_over_cdt.htm">CDT Overview</a>
</p>
<p>
<img src="../images/ngtasks.gif" ALT="Related tasks" width="143"
height="21"> <br> <a
href="../tasks/cdt_t_add_codetemp.htm">Creating and editing
templates</a> <br> <a href="../tasks/cdt_t_contentassist.htm">Using
templates</a> <br> <a href="../tasks/cdt_t_imp_code_temp.htm">Importing
and exporting templates</a>
</p>
<p>
<img src="../images/ngref.gif" ALT="Related reference" width="143"
height="21"> <br> <a href="../reference/cdt_u_m_edit.htm">Edit
menu</a> <br> <a href="../reference/cdt_u_c_editor_con_assist.htm">Content
Assist page</a> <br> <a href="../reference/cdt_u_code_temp.htm">Templates
page</a>
</p>
<p>
<img alt="Red Hat Copyright Statement" src="../images/rh03_04.gif"><br>
<img alt="IBM Copyright Statement" src="../images/ng00_04a.gif">
</p>
</div>
</body>
</html>

55
debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_views.htm
View file

@ -1,55 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Views in the C/C++ perspective</title>
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<div role="main">
<h1>C/C++ Views</h1>
<p>The C/C++ views are panels that help you perform the tasks involved in managing C/C++ programs.
These views can be added to the <a href="cdt_c_perspectives.htm">perspective</a> for your Eclipse window. </p>
<strong>Changing Views:</strong>
<ul>
<li>You can add views to a perspective. From the menu bar choose <strong>Window > Show View</strong> and select a new view from one of the
categories of views in the Show View dialog.</li>
<li>To reset the current perspective to its original layout, from the menu bar choose <strong>Window > Reset Perspective</strong>.</li>
</ul>
<p>The following views are commonly used in the <strong>C/C++</strong> perspective:</p>
<dl>
<dt>Project Explorer</dt><dd>Shows all of the file system's files under your workspace directory.</dd>
<dt>Console</dt><dd>Displays your program's output, as well as the output from your build tools.</dd>
<dt>Editor</dt><dd>The C/C++ editor view provides specialized features for editing C/C++ related files.</dd>
<dt>Outline</dt><dd>Displays the structure of the file currently open in an editor.</dd>
<dt>Problems</dt>
<dd>If you encounter any errors during a build they will be displayed in the Problems view.</dd>
<dt>Properties</dt><dd>Shows the attributes of the item currently selected in a view or an editor.</dd>
<dt>Tasks</dt><dd>Lists tasks that want to keep track of, either as a schedule of things to do or a history of things that have been done.</dd>
</dl>
<p><img src="../images/ngconcepts.gif" ALT="Related concepts" width="143" height="21">
<br><a href="cdt_c_over_cdt.htm">CDT Overview</a>
<br><a href="cdt_c_perspectives.htm">Perspectives</a>
</p>
<p><img src="../images/ngref.gif" ALT="Related reference" width="143" height="21">
<br><a href="../reference/cdt_o_views.htm">Views</a>
</p>
<p>
<img src="../images/rh03_04.gif" ALT="Red Hat Copyright Statement"><br>
<img src="../images/ng00_07.gif" ALT=" IBM Copyright Statement" >
</p>
</div>
</body>
</html>

23
debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_whatsnew.htm
View file

@ -1,23 +0,0 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en" dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="keywords" content="CDT/User/NewInCDT" />
<title>CDT New and Noteworthy</title>
</head>
<body>
<div>
<h1 id="top">CDT - New and Noteworthy</h1>
<p>See <a href="https://github.com/eclipse-cdt/cdt/blob/main/NewAndNoteworthy/README.md">What's new in CDT</a>
which contains the most recent information.
</p>
<p><a href="#top">Back to Top</a></p>
<p>&nbsp;</p>
</div>
</body>
</html>

24
debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_o_build_conc.htm
View file

@ -1,24 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Build</title>
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<div role="main">
<h1>Build</h1>
<p>This section describes the build views and terminology.</p>
<img src="../images/trans.gif" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_c_build_over.htm">Building C/C++ Projects</a><br>
<img src="../images/trans.gif" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_c_scanner_discovery.htm">Scanner Discovery of include paths and preprocessor macros</a><br>
<p><img src="../images/ng00_04a.gif" ALT="IBM Copyright Statement" ></p>
</div>
</body>
</html>

23
debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_o_code_entry.htm
View file

@ -1,23 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Coding aids</title>
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<div role="main">
<h1>Coding aids</h1>
<p>This section provides information on code entry aids.</p>
<img src="../images/trans.gif" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_c_comments.htm">Comments</a><br>
<img src="../images/trans.gif" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_c_content_assist.htm">Content Assist</a><br>
<img src="../images/trans.gif" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_c_templates.htm">Templates</a><br>
<p><img src="../images/ng00_04a.gif" ALT="IBM Copyright Statement" ></p>
</div>
</body>
</html>

60
debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_o_concepts.htm
View file

@ -1,60 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Concepts</title>
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<div role="main">
<h1>Concepts</h1>
<p>Provides background information for CDT components, tasks and objectives.</p>
<img src="../images/trans.gif" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_c_over_cdt.htm">CDT Overview</a><br>
<img src="../images/trans.gif" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_c_projects.htm">CDT Projects</a><br>
<img src="../images/trans.gif" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_c_perspectives.htm">Perspectives available to C/C++ developers</a><br>
<img src="../images/trans.gif" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_c_views.htm">Views in the C/C++ perspective</a><br>
<img src="../images/trans.gif" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_o_code_entry.htm">Coding aids</a><br>
<img src="../images/trans.gif" width="50" height="1" alt=""><a style="text-decoration:none" href="cdt_c_comments.htm">Comments</a><br>
<img src="../images/trans.gif" width="50" height="1" alt=""><a style="text-decoration:none" href="cdt_c_content_assist.htm">Content Assist</a><br>
<img src="../images/trans.gif" width="50" height="1" alt=""><a style="text-decoration:none" href="cdt_c_templates.htm">Templates</a><br>
<img src="../images/trans.gif" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_o_edit.htm">Editing C/C++ Files</a><br>
<img src="../images/trans.gif" width="50" height="1" alt=""><a style="text-decoration:none" href="cdt_c_editor.htm">C/C++ editor</a><br>
<img src="../images/trans.gif" width="50" height="1" alt=""><a style="text-decoration:none" href="cdt_c_makefile.htm">Makefile</a><br>
<img src="../images/trans.gif" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_o_nav.htm">Navigation aids</a><br>
<img src="../images/trans.gif" width="50" height="1" alt=""><a style="text-decoration:none" href="cdt_c_outlineview.htm">Outline View</a><br>
<img src="../images/trans.gif" width="50" height="1" alt=""><a style="text-decoration:none" href="cdt_c_proj_file_views.htm">Project File views</a><br>
<img src="../images/trans.gif" width="50" height="1" alt=""><a style="text-decoration:none" href="cdt_c_search.htm">C/C++ Search</a><br>
<img src="../images/trans.gif" width="50" height="1" alt=""><a style="text-decoration:none" href="cdt_c_open_declarations.htm">Open Declaration</a><br>
<!--
<img src="../images/trans.gif" width="50" height="1" alt=""><a style="text-decoration:none">Open Element</a><br>
<img src="../images/trans.gif" width="50" height="1" alt=""><a style="text-decoration:none">Type Hierarchy</a><br>
<img src="../images/trans.gif" width="50" height="1" alt=""><a style="text-decoration:none">Call Hierarchy</a><br>
<img src="../images/trans.gif" width="50" height="1" alt=""><a style="text-decoration:none">Include Browser</a><br>
<img src="../images/trans.gif" width="50" height="1" alt=""><a style="text-decoration:none">Make Targets View</a><br>
-->
<img src="../images/trans.gif" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_o_build_conc.htm">Build</a><br>
<img src="../images/trans.gif" width="50" height="1" alt=""><a style="text-decoration:none" href="cdt_c_build_over.htm">Building C/C++ Projects</a><br>
<img src="../images/trans.gif" width="50" height="1" alt=""><a style="text-decoration:none" href="cdt_c_scanner_discovery.htm">Scanner Discovery of include paths and preprocessor macros</a><br>
<img src="../images/trans.gif" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_o_dbg_concepts.htm">Debug</a><br>
<img src="../images/trans.gif" width="50" height="1" alt=""><a style="text-decoration:none" href="cdt_c_brkpnts.htm">Breakpoints</a><br>
<img src="../images/trans.gif" width="50" height="1" alt=""><a style="text-decoration:none" href="cdt_c_over_dbg.htm">Debug overview</a><br>
<img src="../images/trans.gif" width="50" height="1" alt=""><a style="text-decoration:none" href="cdt_c_dbg_info.htm">Debug information</a><br>
<!--
<img src="../images/trans.gif" width="50" height="1" alt=""><a style="text-decoration: none;">Error Parsing</a><br>
<img src="../images/trans.gif" width="50" height="1" alt=""><a style="text-decoration: none;">Invoking Make</a><br>
-->
<img src="../images/trans.gif" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_c_search.htm">C/C++ search</a><br>
<img src="../images/trans.gif" width="50" height="1" alt=""><a style="text-decoration:none" href="cdt_c_indexer.htm">C/C++ Indexer</a><br>
<img src="../images/trans.gif" width="50" height="1" alt=""><a style="text-decoration:none" href="cdt_c_indexer_prog_bar.htm">C/C++ Indexer Progress Bar</a><br>
<p><img src="../images/ng00_07.gif" ALT="IBM Corporation Statement" ></p>
</div>
</body>
</html>

23
debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_o_dbg_concepts.htm
View file

@ -1,23 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Debug</title>
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<div role="main">
<h1>Debug</h1>
<p>This section describes C/C++ debug concepts.</p>
<img src="../images/trans.gif" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_c_brkpnts.htm">Breakpoints</a><br>
<img src="../images/trans.gif" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_c_over_dbg.htm">Debug overview</a><br>
<img src="../images/trans.gif" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_c_dbg_info.htm">Debug information</a><br>
<p><img src="../images/ng00_04a.gif" ALT="IBM Copyright Statement" ></p>
</div>
</body>
</html>

20
debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_o_edit.htm
View file

@ -1,20 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Editing C/C++ Files</title>
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<div role="main">
<h1>Editing C/C++ Files</h1>
<p>This section provides information on editing C/C++ files.</p>
<img src="../images/trans.gif" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_c_editor.htm">C/C++ editor</a><br>
<p><img src="../images/ng00_07.gif" ALT="IBM Copyright Statement" ></p>
</div>
</body>
</html>

36
debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_o_home.htm
View file

@ -1,36 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>C/C++ Development User Guide</title>
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<div role="main">
<h1>C/C++ Development User Guide</h1>
<p>The C/C++ Development Toolkit (CDT) is a collection of Eclipse-based features that provides the capability
to create, edit, navigate, build, and debug projects that use C and/or C++ as a programming language.</p>
<p>The CDT does not include the necessary compilers and debuggers to convert C/C++ code into executable
programs and to debug those programs, but it does provide the frameworks that allow such tools to
be integrated in a consistent fashion.
This allows you to mix and match such tools depending on your project requirements.</p>
<p>Often, commercial distributions of the CDT include the necessary tools and integrations. If yours does
not, the base CDT does provide support for integration with the GNU tools for build and debug. Please see the
<a href="cdt_c_before_you_begin.htm">Before you begin</a> section for installation instructions</p>
<img src="../images/trans.gif" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_c_before_you_begin.htm">Before you begin</a><br>
<br>
<img src="../images/trans.gif" width="25" height="1" alt=""><a style="text-decoration:none" href="../getting_started/cdt_o_tutorial.htm">Getting Started</a><br>
<img src="../images/trans.gif" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_o_concepts.htm">Concepts</a><br>
<img src="../images/trans.gif" width="25" height="1" alt=""><a style="text-decoration:none" href="../tasks/cdt_o_tasks.htm">Tasks</a><br>
<img src="../images/trans.gif" width="25" height="1" alt=""><a style="text-decoration:none" href="../reference/cdt_o_ref.htm">Reference</a><br>
<br>
<img src="../images/trans.gif" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_c_whatsnew.htm">What's new</a><br>
</div>
</body>
</html>

29
debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_o_nav.htm
View file

@ -1,29 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html lang="en">
<head>
<meta http-equiv="Content-Language" content="en-us">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Navigation Aids</title>
<link rel="stylesheet" type="text/css" href="../help.css">
</head>
<body>
<div role="main">
<h1>Navigation Aids</h1>
<p>This section provides information on navigating through the C/C++ Perspective.</p>
<img src="../images/trans.gif" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_c_outlineview.htm">Outline View</a><br>
<img src="../images/trans.gif" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_c_proj_file_views.htm">Project File views</a><br>
<img src="../images/trans.gif" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_c_search.htm">C/C++ Search</a><br>
<img src="../images/trans.gif" width="25" height="1" alt=""><a style="text-decoration:none" href="cdt_c_open_declarations.htm">Open Declaration</a><br>
<!--
<img src="../images/trans.gif" width="25" height="1" alt=""><a style="text-decoration:none">Open Element</a><br>
<img src="../images/trans.gif" width="25" height="1" alt=""><a style="text-decoration:none">Type Hierarchy</a><br>
<img src="../images/trans.gif" width="25" height="1" alt=""><a style="text-decoration:none">Call Hierarchy</a><br>
<img src="../images/trans.gif" width="25" height="1" alt=""><a style="text-decoration:none">Include Browser</a><br>
<img src="../images/trans.gif" width="25" height="1" alt=""><a style="text-decoration:none">Make Targets View</a><br>
-->
<p><img src="../images/ng00_07.gif" ALT="IBM Copyright Statement" ></p>
</div>
</body>
</html>

163
debug/org.eclipse.cdt.debug.application.doc/customBuildCallbacks.xml
View file

@ -1,163 +0,0 @@
<!-- ===================================================================== -->
<!-- Custom targets called from a project's generated build.xml -->
<!-- Set customBuildCallbacks=<path/to/this/file> in your build.properties.-->
<!-- ===================================================================== -->
<project name="Build specific targets and properties" default="noDefault">
<!-- ===================================================================== -->
<!-- Default target -->
<!-- ===================================================================== -->
<target name="noDefault">
<echo message="This file must be called with explicit targets" />
</target>
<!-- ===================================================================== -->
<!-- Steps to do before the target build.jars -->
<!-- Available parameters : -->
<!-- build.result.folder - folder to contain the build results -->
<!-- ===================================================================== -->
<target name="pre.build.jars">
</target>
<!-- ===================================================================== -->
<!-- Steps to do after the target build.jars -->
<!-- Available parameters : -->
<!-- build.result.folder - folder to contain the build results -->
<!-- ===================================================================== -->
<target name="post.build.jars">
<antcall target="build.index"/>
</target>
<target name="build.index" description="Builds search index for the plug-in: org.eclipse.rse.doc.user." if="eclipse.running">
<help.buildHelpIndex manifest="plugin.xml" destination="."/>
</target>
<!-- ===================================================================== -->
<!-- Steps to do before the target build.sources -->
<!-- Available parameters : -->
<!-- build.result.folder - folder to contain the build results -->
<!-- ===================================================================== -->
<target name="pre.build.sources">
</target>
<!-- ===================================================================== -->
<!-- Steps to do after the target build.sources -->
<!-- Available parameters : -->
<!-- build.result.folder - folder to contain the build results -->
<!-- ===================================================================== -->
<target name="post.build.sources">
</target>
<!-- ===================================================================== -->
<!-- Steps to do before the compilation target <name> -->
<!-- Substitute "name" with the name of the compilation target, eg @dot -->
<!-- Available parameters : -->
<!-- source.foldern : n = 1 ... N, the source folders -->
<!-- target.folder : where the results of the compilation go -->
<!-- <name>.classpath : name = name of the compilation target. A -->
<!-- reference to the classpath structure. -->
<!-- ===================================================================== -->
<target name="pre.name">
</target>
<target name="pre.@dot">
</target>
<!-- ===================================================================== -->
<!-- Steps to do during the compilation target <name>, after the compile -->
<!-- but before jaring. Substitute "name" with the name of the compilation-->
<!-- target, eg @dot -->
<!-- Available parameters : -->
<!-- source.foldern : n = 1 ... N, the source folders -->
<!-- target.folder : where the results of the compilation go -->
<!-- <name>.classpath : name = name of the compilation target. A -->
<!-- reference to the classpath structure. -->
<!-- ===================================================================== -->
<target name="post.compile.name">
</target>
<target name="post.compile.@dot">
</target>
<!-- ===================================================================== -->
<!-- Steps to do after the compilation target <name> -->
<!-- Substitute "name" with the name of the compilation target, eg @dot -->
<!-- Available parameters : -->
<!-- jar.Location - the location of the compilation results -->
<!-- <name>.classpath : name = name of the compilation target. A -->
<!-- reference to the classpath structure. -->
<!-- ===================================================================== -->
<target name="post.name">
</target>
<target name="post.@dot">
</target>
<!-- ===================================================================== -->
<!-- Steps to do before the target gather.bin.parts -->
<!-- Available parameters : -->
<!-- build.result.folder - folder containing the build results -->
<!-- target.folder - destination folder -->
<!-- ===================================================================== -->
<target name="pre.gather.bin.parts">
</target>
<!-- ===================================================================== -->
<!-- Steps to do after the target gather.bin.parts -->
<!-- Available parameters : -->
<!-- build.result.folder - folder containing the build results -->
<!-- target.folder - destination folder -->
<!-- ===================================================================== -->
<target name="post.gather.bin.parts">
</target>
<!-- ===================================================================== -->
<!-- Steps to do before the target gather.sources -->
<!-- Available parameters : -->
<!-- destination.temp.folder - destination folder -->
<!-- ===================================================================== -->
<target name="pre.gather.sources">
</target>
<!-- ===================================================================== -->
<!-- Steps to do after the target gather.sources -->
<!-- Available parameters : -->
<!-- destination.temp.folder - destination folder -->
<!-- ===================================================================== -->
<target name="post.gather.sources">
</target>
<!-- ===================================================================== -->
<!-- Steps to do before the target gather.logs -->
<!-- Available parameters : -->
<!-- destination.temp.folder - destination folder -->
<!-- ===================================================================== -->
<target name="pre.gather.logs">
</target>
<!-- ===================================================================== -->
<!-- Steps to do after the target gather.logs -->
<!-- Available parameters : -->
<!-- destination.temp.folder - destination folder -->
<!-- ===================================================================== -->
<target name="post.gather.logs">
</target>
<!-- ===================================================================== -->
<!-- Steps to do before the target clean -->
<!-- Available parameters : -->
<!-- destination.temp.folder - destination folder -->
<!-- ===================================================================== -->
<target name="pre.clean">
</target>
<!-- ===================================================================== -->
<!-- Steps to do after the target clean -->
<!-- Available parameters : -->
<!-- plugin.destination - final destination of the build -->
<!-- build.result.folder - results of the compilation -->
<!-- temp.folder - temporary folder -->
<!-- ===================================================================== -->
<target name="post.clean">
</target>
</project>

13
debug/org.eclipse.cdt.debug.application.doc/html/maintopic.html
View file

@ -1,13 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>Main Topic</title>
</head>
<body>
<h1>Main Topic</h1>
Please enter your text here.
</body>
</html>

13
debug/org.eclipse.cdt.debug.application.doc/html/subtopic.html
View file

@ -1,13 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>Sub Topic</title>
</head>
<body>
<h1>Sub Topic</h1>
Please enter your text here.
</body>
</html>

13
debug/org.eclipse.cdt.debug.application.doc/html/toc.html
View file

@ -1,13 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>Table of Contents</title>
</head>
<body>
<h1>Table of Contents</h1>
Please enter your text here.
</body>
</html>

BIN
debug/org.eclipse.cdt.debug.application.doc/images/add_breakpoint.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 6.1 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/alphab_sort_co.gif
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 224 B

BIN
debug/org.eclipse.cdt.debug.application.doc/images/btn_columns.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 597 B

BIN
debug/org.eclipse.cdt.debug.application.doc/images/btn_import_executables.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 606 B

BIN
debug/org.eclipse.cdt.debug.application.doc/images/btn_restart.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 590 B

BIN
debug/org.eclipse.cdt.debug.application.doc/images/builder_settings.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 62 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/c_cpp_preferences.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 44 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/c_element_filters.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 11 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/c_exe_obj.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 736 B

BIN
debug/org.eclipse.cdt.debug.application.doc/images/c_file_obj.gif
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 354 B

BIN
debug/org.eclipse.cdt.debug.application.doc/images/c_object_file.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 699 B

BIN
debug/org.eclipse.cdt.debug.application.doc/images/c_ovr.gif
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 81 B

BIN
debug/org.eclipse.cdt.debug.application.doc/images/c_paths.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 50 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/cdt_autobuild.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 28 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/cdt_buildenv_newenvvar.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 9 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/cdt_buildenv_selectvar.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 26 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/cdt_ca_no_completions.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 469 B

BIN
debug/org.eclipse.cdt.debug.application.doc/images/cdt_debug_bp_filter.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 5.2 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/cdt_debug_exes01.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 20 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/cdt_debug_exes02.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 17 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/cdt_debug_exes03.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 16 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/cdt_debug_exes04.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 32 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/cdt_debug_exes05.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 6.5 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/cdt_debug_hover_modes.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 5.4 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/cdt_debug_run01.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 4.8 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/cdt_dlg_define_build_var.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 12 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/cdt_dlg_edit_build_var.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 12 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/cdt_dsfgdb_preferences_page.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 121 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/cdt_error_workbench.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 71 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/cdt_file_inc.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 58 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/cdt_file_steps.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 37 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/cdt_file_sym.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 57 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/cdt_file_toolsett.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 32 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/cdt_fold_resource.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 26 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/cdt_fold_toolsett.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 43 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/cdt_inline_rename.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 10 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/cdt_menu_toggle_comments.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 4.2 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/cdt_menubar.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 19 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/cdt_new_brk_action.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 19 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/cdt_open_element.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 27 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref-multi-cfg.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 45 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref-prop-pages.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 108 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref-wizard-defaults.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 35 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref-wizard-toolchains.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 44 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref_brk_action.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 34 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref_brk_action_properties.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 18 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref_build_console.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 41 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref_build_vars.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 66 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref_file_types.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 36 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref_new_task_tag_dlg.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 9 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/cdt_pref_task_tags.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 42 KiB

BIN
debug/org.eclipse.cdt.debug.application.doc/images/cdt_refactor.png
View file

Binary file not shown.
Side by side

Before

Width:  |  Height:  |  Size: 55 KiB

Some files were not shown because too many files have changed in this diff Show more