Find a file
Umair Sair b10979677e Cleaning project fails once the binary is expanded in project explorer on Windows
Steps:
======
1. Create a managed project and build it
2. Expand the built binary available in binary container in project explorer view
3. Now clean the project, clean will fail irrespective of number of tries you do

Reason:
=======
For finding the sources for binary, Elf instance is created and Section.mapSectionData creates MappedByteBuffer of channel which locks the file on Windows until its garbage collected, see following
https://bugs.java.com/bugdatabase/view_bug.do?bug_id=4715154

Solution:
=========
Made ISymbolReader AutoCloseable and user is responsible to properly close it. In case of dwarf reader, we remove all the references of ByteBuffer and call gc.
2022-11-07 17:32:17 -05:00
.github/workflows Enable the profile in the GH Actions to verify standalone builds 2022-10-25 22:29:07 -04:00
.mvn [releng] Update to Tycho 2.7.1 2022-04-11 17:07:30 -04:00
build Make tests inherit from BaseTestCase or BaseTestCase5 2022-11-07 10:04:20 -05:00
cmake Upgrade build.properties warnings to errors 2022-11-06 18:29:28 -05:00
codan Add JUnit5 dependencies 2022-11-07 10:04:20 -05:00
core Cleaning project fails once the binary is expanded in project explorer on Windows 2022-11-07 17:32:17 -05:00
cross Upgrade build.properties warnings to errors 2022-11-06 18:29:28 -05:00
debug Cleaning project fails once the binary is expanded in project explorer on Windows 2022-11-07 17:32:17 -05:00
doc Upgrade build.properties warnings to errors 2022-11-06 18:29:28 -05:00
dsf Upgrade build.properties warnings to errors 2022-11-06 18:29:28 -05:00
dsf-gdb Wait until all threads are stopped before continuing test 2022-11-07 10:04:20 -05:00
FAQ Add some links for CDT indexer FAQ 2022-10-07 13:57:02 -04:00
images Improve documentation on how to run JUnit tests 2022-11-06 18:27:56 -05:00
jenkins/pod-templates Migrate builds to GitHub as source (#26) 2022-08-08 09:07:31 -04:00
jsoncdb Upgrade build.properties warnings to errors 2022-11-06 18:29:28 -05:00
jtag Upgrade build.properties warnings to errors 2022-11-06 18:29:28 -05:00
launch Upgrade build.properties warnings to errors 2022-11-06 18:29:28 -05:00
launchbar Upgrade build.properties warnings to errors 2022-11-06 18:29:28 -05:00
llvm Upgrade build.properties warnings to errors 2022-11-06 18:29:28 -05:00
lsp Upgrade build.properties warnings to errors 2022-11-06 18:29:28 -05:00
memory Upgrade build.properties warnings to errors 2022-11-06 18:29:28 -05:00
native Upgrade build.properties warnings to errors 2022-11-06 18:29:28 -05:00
NewAndNoteworthy Cleaning project fails once the binary is expanded in project explorer on Windows 2022-11-07 17:32:17 -05:00
releng Upgrade build.properties warnings to errors 2022-11-06 18:29:28 -05:00
remote Upgrade build.properties warnings to errors 2022-11-06 18:29:28 -05:00
terminal Upgrade build.properties warnings to errors 2022-11-06 18:29:28 -05:00
testsrunner Upgrade build.properties warnings to errors 2022-11-06 18:29:28 -05:00
tools.templates Upgrade build.properties warnings to errors 2022-11-06 18:29:28 -05:00
unittest Upgrade build.properties warnings to errors 2022-11-06 18:29:28 -05:00
util Upgrade build.properties warnings to errors 2022-11-06 18:29:28 -05:00
visualizer Upgrade build.properties warnings to errors 2022-11-06 18:29:28 -05:00
windows Upgrade build.properties warnings to errors 2022-11-06 18:29:28 -05:00
.clang-format Bug 568079: Reformat source code using clang-format 2020-10-31 20:13:42 -04:00
.gitattributes Migrate New and Noteworthy from Wiki to GitHub 2022-10-02 20:46:56 -04:00
.gitignore GitHub Action for Code Cleanliness Check 2022-10-09 12:14:53 -04:00
.project Filter nested projects from org.eclipse.cdt.root 2022-08-12 09:39:25 +02:00
BUILDING.md DSF-GDB tests in GitHub Actions 2022-10-10 08:44:28 -04:00
CODE_OF_CONDUCT.md Split apart the README file and update Contributing file from the wiki 2022-08-04 12:23:12 -04:00
CONTRIBUTING.md Improve documentation on how to run JUnit tests 2022-11-06 18:27:56 -05:00
Downloads.md Fix development buid download links 2022-10-20 12:54:47 +01:00
GitHubMigration.md Part of #32: Document the redirects for eclipse.org/cdt to GitHub (#60) 2022-08-22 20:36:41 -04:00
Jenkinsfile Use correct version of GDB on Jenkins 2022-11-07 10:04:20 -05:00
LICENSE Add missing root LICENSE file 2021-11-29 17:58:48 -05:00
POLICY.md Migrate API changelog from HTML into Markdown 2022-10-09 13:24:47 -04:00
pom.xml Remove non-functioning Qt plug-ins 2022-10-29 18:56:47 -04:00
README.md Migrate https://wiki.eclipse.org/CDT:Addons to main repo 2022-10-07 13:57:02 -04:00
TESTING.md Improve documentation on how to run JUnit tests 2022-11-06 18:27:56 -05:00

Eclipse CDT™ C/C++ Development Tools

Jenkins Jenkins tests GitHub Eclipse Marketplace GitHub contributors

The Eclipse CDT™ Project provides a fully functional C and C++ Integrated Development Environment based on the Eclipse platform. Features include: support for project creation and managed build for various toolchains, standard make build, source navigation, various source knowledge tools, such as type hierarchy, call graph, include browser, macro definition browser, code editor with syntax highlighting, folding and hyperlink navigation, source code refactoring and code generation, visual debugging tools, including memory, registers, and disassembly viewers.

Highlights of recent releases and release notes are available in the New & Noteworthy.

See also https://projects.eclipse.org/projects/tools.cdt and https://eclipse.org/cdt

Download

The recommended way to obtain Eclipse CDT is to download it as part of the complete Eclipse IDE for C/C++ Developers or Eclipse IDE for Embedded C/C++ Developers or Eclipse IDE for Scientific Computing from the main Eclipse IDE download site.

Alternatively Eclipse CDT can be installed into an existing Eclipse installation using this p2 URL: https://download.eclipse.org/tools/cdt/releases/latest/ (see how)

Downloads links for older versions are available in Downloads.

Help & Support

The Eclipse CDT (C/C++ Development Tools) User Guide can be found in the Eclipse Help - C/C++ Development User Guide.

The Eclipse forum for C/C++ IDE (CDT) is for users to ask questions on how to use Eclipse CDT. It is monitored by fellow users in the community for support. Stack Overflow also has an eclipse-cdt tag that can be added to questions or searched for prevous similar questions.

The Eclipse CDT Plug-in Developer Guide can also be found in the Eclipse Help - CDT Plug-in Developer Guide.

There is an FAQ covering many commonly asked questions for both user and developers and a Contribution Guide for guidance on editing Eclipse CDT's source and submitting changes.

Reporting issues

Please report issues in the GitHub issue tracker.

Vendor Supplied Eclipse CDT

Did you get your version of Eclipse CDT from a vendor (such as a chip maker)? If so, they generally support their customers. In that case issues and support questions should be directed at the vendor in the first instance.

We encourage all vendors who are extending and redistributing Eclipse CDT to engage with the project and contribute fixes and improvements back to the Eclipse CDT project.

Contributing

Contributions are always welcome!

Please bear in mind that this project is almost entirely developed by volunteers. If you do not provide the implementation yourself (or pay someone to do it for you), the bug might never get fixed. If it is a serious bug, other people than you might care enough to provide a fix.

Add-ons for CDT

There are many third-party addons for CDT to make it more productive.

  • cmake4eclipse: This Eclipse plug-in automatically generates build-scripts for the Eclipse CDT managed build system from CMake scripts.
  • Sloeber: Eclipse Plugins based on Arduino toolchains or a enhanced Arduino IDE.
  • CUTE: C++ unit testing plug-in
  • Bracketeer: Auto-comments on closing brackets and highlight of matching/mismatching brackets
  • And many more in the Eclipse Marketplace, for example, try the CDT tag

Have a tool that you want listed here? Please open a PR

Code of Conduct

This project follows the Eclipse Community Code of Conduct.

Migration from Gerrit, Bugzilla, Wiki, Eclipse Forums

In the summer of 2022 the Eclipse CDT project migrated from Gerrit, Bugzilla, Wiki, Eclipse Forums to GitHub based solutions. Please see GitHub Migration for more details.