eclipse-linuxtools 3.1.0-1 source package in Ubuntu


eclipse-linuxtools (3.1.0-1) unstable; urgency=medium

  [ Jakub Adam ]
  * New upstream release (Closes: #761524).
  * Refreshed d/patches.
  * Don't build removed feature
    - merged into org.eclipse.linuxtools.profiling.
  * Use javac target 1.7.
  * Build new feature org.eclipse.linuxtools.dataviewers.feature
    - required by Valgrind integration.
  * Build-depend on eclipse-remote-services-api and eclipse-cdt-autotools.
  * Bump Standards-Version to 3.9.6.
  * Override incompatible-java-bytecode-format - linuxtools needs Java 7.
  * Remove unused codeless-jar override.

  [ tony mancill ]
  * Tweak short package description to make lintian happy.

 -- Jakub Adam <email address hidden>  Sat, 11 Oct 2014 11:44:05 +0200

Upload details

Uploaded by:
Debian Java Maintainers on 2014-10-15
Uploaded to:
Original maintainer:
Debian Java Maintainers
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Cosmic release on 2018-05-01 universe devel
Bionic release on 2017-10-24 universe devel
Artful release on 2017-04-20 universe devel
Xenial release on 2015-10-22 universe devel


Vivid: [FULLYBUILT] amd64


File Size SHA-256 Checksum
eclipse-linuxtools_3.1.0-1.dsc 2.5 KiB e8cc75b6f786a934e85670ecabd1354ded1acdb515a03abb57493dd376dff0f8
eclipse-linuxtools_3.1.0.orig.tar.xz 20.8 MiB f131a74d20a27c026f71cf2af1a5e705db7a8b8b4eccfe21898b168e7aa7038c
eclipse-linuxtools_3.1.0-1.debian.tar.xz 11.1 KiB dbe2073a98c2461bf28f0bd63849a42af1e0d01a29fa7d6dcfd634394e8f48d6

Available diffs

No changes file available.

Binary packages built by this source

eclipse-cdt-perf: No summary available for eclipse-cdt-perf in ubuntu vivid.

No description available for eclipse-cdt-perf in ubuntu vivid.

eclipse-cdt-profiling-framework: framework for profiling tools for Eclipse CDT

 This package provides a common infrastructure that allows one to integrate
 various profiling tools into Eclipse IDE. It supports 3 categories of tools:
  * Timing - measure the amount of time taken in functions and methods
  * Memory - profiles heap/stack/cache usage for an application
  * Coverage - measures how much of the code gets exercised in a run
 In addition to this package, a plugin that integrates particular profiling tool
 (e.g. Valgrind or perf) is required in order to run performance analysis.

eclipse-cdt-profiling-framework-remote: No summary available for eclipse-cdt-profiling-framework-remote in ubuntu disco.

No description available for eclipse-cdt-profiling-framework-remote in ubuntu disco.

eclipse-cdt-valgrind: Valgrind integration for Eclipse CDT

 The Linux Tools Project Valgrind plugin aims to provide simple and effective
 profiling for the C/C++ Development Tools.
 Integration of these tools from Valgrind suite is provided:
  * Memcheck *
 Memcheck is a tool that detects memory management problems. It is Valgrind's
 most popular tool and seemingly the most mature. Memcheck's output is rather
 straight forward - it is a series of errors along with stack trace information.
 The Valgrind View presents this output using a TreeViewer with the errors as
 top-level elements.
 The stack trace is presented underneath the error and when a frame is
 double-clicked an editor will open and go to the line in question.
 Markers represent memcheck errors inside the editor and are linked to the
 Problems View.
 Includes an editor for Valgrind suppressions files featuring syntax
 highlighting, folding and code completion.
  * Massif *
 Massif is a heap profiling tool. It takes several "snapshots" during execution
 of your program detailing the various heap allocations throughout. It's output
 for each snapshot primarily consists the time of the snapshot, how many bytes
 were allocated that can be used, and how much extra was allocated than was
 asked. The unit of time can be configured to be instructions, milliseconds or
 bytes. At specified intervals, "detailed" snapshots are produced. These
 detailed snapshots contain a tree of heap allocations that comprise that
 snapshot. Unlike Memcheck, Massif does not yet support XML output. Massif's
 output is complex and as such requires creative ways of displaying it. Valgrind
 includes the ms_print program that is used to display Massif's output in a
 visually appealing manner. ms_print was used as a template for how to display
 this output.
 The default view of the output is with a TableViewer. Snapshots are displayed
 as tabular data, just as ms_print does.
 For detailed snapshots, an icon indicates the snapshot can be double-clicked
 and the View will display a TreeViewer of the detailed snapshots' heap
 allocation trees.
 ms_print also provides a bar chart of bytes allocated throughout execution. In
 perhaps a more appropriate style, there is an option to display a detailed line
 chart of this data.
 * Cachegrind *
 Cachegrind performs cache and branching profiling. A Cachegrind profile run
 measures the number of cache misses and branch mispredictions performed by an
 application. The results of a Cachegrind profile run are displayed in the
 Valgrind view. These results show Cachegrind's cache/branch data in different
 levels of granularity.
 Double-clicking on any file, function, or line will open the corresponding
 source file and place the cursor on the appropriate location (if the source can
 be resolved).
 Integration with the CDT's parsed code model provides a user interface that
 resembles what you see in the Outline view.

eclipse-changelog: No summary available for eclipse-changelog in ubuntu vivid.

No description available for eclipse-changelog in ubuntu vivid.

eclipse-rpm-editor: No summary available for eclipse-rpm-editor in ubuntu disco.

No description available for eclipse-rpm-editor in ubuntu disco.