Bug 447554 - gcov not handling linked files

- Fix number of runs counter to come from program summary
  instead of object summary as that has been obsoleted
- Fix logic to handle case where we end up with an IFileEditorInput
  and we want an IFileStore (don't return null and end up
  using a source-not-found editor)
- Add a method to get all projects we are tracking for gcov
- Add a visitor class to search a project for a linked-in
  resource we are trying to open from the gcov view

Change-Id: Ieeb4c8a047a95da239e7b625f717a1d44fad8f31
Reviewed-on: https://git.eclipse.org/r/35155
Reviewed-by: Roland Grunberg <rgrunber@redhat.com>
Tested-by: Roland Grunberg <rgrunber@redhat.com>
(cherry picked from commit 75704836bd061a8d66588792170d9528a0946b3c)
Reviewed-on: https://git.eclipse.org/r/35156
Tested-by: Hudson CI
Reviewed-by: Jeff Johnston <jjohnstn@redhat.com>
Tested-by: Jeff Johnston <jjohnstn@redhat.com>
5 files changed
tree: 44a4b18393a7e3ae7840242a59ea1949190fb99f
  1. changelog/
  2. gcov/
  3. gprof/
  4. libhover/
  5. lttng/
  6. man/
  7. oprofile/
  8. perf/
  9. profiling/
  10. releng/
  11. rpm/
  12. systemtap/
  13. valgrind/
  14. .gitignore
  15. pom.xml
  16. 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.

Contributor License Agreement:

Before your contribution can be accepted by the project, you need to create and electronically sign the Eclipse Foundation Contributor License Agreement (CLA).

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!