Skip to content
Linux Tools project repository (linuxtools)
Java HTML C CSS C++ Shell
Latest commit c2364c0 Apr 29, 2016 Roberto Oliveira Bug 492740: Fix Valgrind/Memcheck quick fixes not working in local pr…
…ojects

Change-Id: Ibe5557445db1b8d134361260e23d8e88cf3bc322
Signed-off-by: Roberto Oliveira <rdutra@linux.vnet.ibm.com>
Reviewed-on: https://git.eclipse.org/r/71728
Tested-by: Hudson CI
Failed to load latest commit information.
changelog
containers
gcov
gprof
javadocs
libhover
lttng Remove content of the lttng folder and corresponding target dependencies Mar 6, 2015
man
oprofile
perf
profiling
releng
rpm
systemtap
vagrant Use a distinct icon for Vagrant Tooling perspective. Apr 5, 2016
valgrind
.gitignore
README.md Better README.md. Mar 26, 2014
pom.xml releng: Build with Tycho 0.25. Apr 21, 2016

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!

Something went wrong with that request. Please try again.