Bug 575368 - Exception when opening GCov coverage files on Cygwin GCC

- change Arc constructor to check flag values one by one and set
  each boolean variable appropriately instead of always setting
  one value to true and the others to false
- also add isThrow() and setIsThrow() methods for later use
- add new hasCatch() and setHasCatch() methods to GcnoFunction
  again for later use
- change GcnoRecordsParser.parseData() method to always read length
  field for tags, even if they are unrecognized and to always skip
  ahead the length either by processing the tag or if unrecognized,
  manually
- also sync up logic to gcc 10.2.0 whereby fnctn is set to null when
  an unrecognized tag shows up that isn't a sub-tag and check for
  fnctn being null before handling various tags
- add logic to mark catches for later use

Change-Id: Ief1203c3951b1aadabca3502517e0ac592694287
Reviewed-on: https://git.eclipse.org/r/c/linuxtools/org.eclipse.linuxtools/+/184434
Tested-by: Linux Tools Bot <linuxtools-bot@eclipse.org>
Reviewed-by: Jeff Johnston <jjohnstn@redhat.com>
3 files changed
tree: 88aaed038fc1e6af1a6eaacb3fc5597f9b8f2171
  1. changelog/
  2. containers/
  3. gcov/
  4. gprof/
  5. javadocs/
  6. libhover/
  7. lttng/
  8. man/
  9. perf/
  10. profiling/
  11. releng/
  12. rpm/
  13. systemtap/
  14. vagrant/
  15. valgrind/
  16. .gitignore
  17. .project
  18. LICENSE
  19. pom.xml
  20. README.md
README.md

Contributing to Linux Tools

Thanks for your interest in this project.

Project description:

The Linux Tools project aims to bring a full-featured C and C++ IDE to Linux developers. We build on the source editing and debugging features of the CDT and integrate popular native development tools such as the GNU Autotools, Valgrind, OProfile, RPM, SystemTap, GCov, GProf, LTTng, etc. Current projects include LTTng trace viewers and analyzers, an RPM .spec editor, Autotools build integration, a Valgrind heap usage analysis tool, and OProfile call profiling tools. The project also provides a place for Linux distributions to collaboratively overcome issues surrounding distribution packaging of Eclipse technology. The project produces both best practices and tools related to packaging. One of our features is a source archive of the Eclipse SDK that can be used by all Linux distributions building and distributing it.

Developer resources:

Information regarding source code management, builds, coding standards, and more.

Eclipse Contributor Agreement:

Before your contribution can be accepted by the project team contributors must electronically sign the Eclipse Contributor Agreement (ECA).

Commits that are provided by non-committers must have a Signed-off-by field in the footer indicating that the author is aware of the terms by which the contribution has been provided to the project. The non-committer must additionally have an Eclipse Foundation account and must have a signed Eclipse Contributor Agreement (ECA) on file.

For more information, please see the Eclipse Committer Handbook: https://www.eclipse.org/projects/handbook/#resources-commit

Contact:

Contact the project developers via the project's “dev” list.

Search for bugs:

This project uses Bugzilla to track ongoing development and issues.

Create a new bug:

Be sure to search for existing bugs before you create another one. Remember that contributions are always welcome!