gcov/gprof: No need for sharedInstance singleton.

If there is no state saved and constructors are empty it's better to
make methods static and use them as such.
Drop useless non-javadoc comments where there are Override annotations.

Change-Id: I0e3156452f9ff7dca282fefaeaf99a049f4fe4e1
Signed-off-by: Alexander Kurtakov <akurtako@redhat.com>
Reviewed-on: https://git.eclipse.org/r/25197
Tested-by: Hudson CI
9 files changed
tree: 4693175ef2330aa7d67c4547167ba60feea115c3
  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!