File: control

package info (click to toggle)
eclipse-linuxtools 3.1.0-1
  • links: PTS, VCS
  • area: main
  • in suites: jessie, jessie-kfreebsd, stretch
  • size: 75,416 kB
  • ctags: 41,034
  • sloc: java: 262,051; xml: 34,770; ansic: 15,458; cpp: 326; sh: 261; makefile: 60
file content (167 lines) | stat: -rw-r--r-- 7,222 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
Source: eclipse-linuxtools
Section: devel
Priority: optional
Maintainer: Debian Java Maintainers <pkg-java-maintainers@lists.alioth.debian.org>
Uploaders: Jakub Adam <jakub.adam@ktknet.cz>
Build-Depends: debhelper (>= 8~),
               default-jdk,
               eclipse-pde (>= 3.7~exp),
               eclipse-cdt (>= 8.0.0),
               eclipse-cdt-autotools,
               eclipse-ptp-rdt,
               eclipse-remote-services-api,	
               javahelper (>= 0.32~),
               libswtchart-java,
               unzip,
               zip
Standards-Version: 3.9.6
Homepage: http://www.eclipse.org/linuxtools/
Vcs-Git: git://anonscm.debian.org/pkg-java/eclipse-linuxtools.git
Vcs-Browser: http://anonscm.debian.org/gitweb/?p=pkg-java/eclipse-linuxtools.git

Package: eclipse-cdt-profiling-framework
Architecture: all
Depends: eclipse-cdt,
         eclipse-cdt-autotools,
         ${misc:Depends},
         ${orbit:Depends}
Description: 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.

Package: eclipse-cdt-profiling-framework-remote
Architecture: all
Depends: eclipse-cdt-profiling-framework,
         eclipse-rse,
         eclipse-ptp-rdt,
         eclipse-remote-services-api,
         ${misc:Depends},
         ${orbit:Depends}
Description: Remote profiling support for Eclipse
 This package allows one to launch profiling tools and acquire data from remote
 targets like embedded systems, that have too limited resources to run a full
 scale IDE.
 .
 In addition to this package, a plugin that integrates particular profiling tool
 is required in order to run performance analysis.

Package: eclipse-cdt-valgrind
Architecture: all
Depends: eclipse-cdt-profiling-framework,
         valgrind,
         ${misc:Depends},
         ${orbit:Depends}
Description: 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.

Package: eclipse-cdt-perf
Architecture: all
Depends: eclipse-cdt-profiling-framework,
         ${misc:Depends},
         ${orbit:Depends}
Recommends: linux-tools
Suggests: eclipse-cdt-profiling-framework-remote
Description: 'perf' analysis tool integration for Eclipse CDT
 'perf' is a performance counters subsystem in Linux. Performance counters are
 CPU hardware registers that count hardware events such as instructions executed
 and cache-misses suffered. These counters aid in profiling applications to
 detect hotspots in the application. 'perf' provides per task, per CPU and
 per-workload counters, sampling on top of these and source code event
 annotation.
 .
 The perf plug-in for Eclipse allows the developer to execute profiles in their
 applications in a seamless way, using quick launch actions and visualizing
 the results in an user-friendly interface.

Package: eclipse-changelog
Architecture: all
Depends: ${misc:Depends},
         ${orbit:Depends}
Description: Automatic ChangeLog entry creation support for Eclipse
 Method and function indication is provided for C, C++, and Java language files.
 The RPM .spec %changelog format is also supported. A ChangeLog entry can be
 created for a single file or an entire project. In addition, a ChangeLog editor
 is provided which makes it easy to format the file consistently and to put the
 latest entry into the clipboard buffer for usage in a repository commit
 operation.

Package: eclipse-rpm-editor
Architecture: all
Depends: eclipse-changelog,
         ${misc:Depends},
         ${orbit:Depends}
Description: Editor for RPM .spec files integrated into Eclipse
 Specfile Editor is a full featured editor for RPM spec files. Specfiles are the
 files that tell the rpm program which are the sources for this package, how to
 build, where to install, additional scripts to execute on install/uninstall and
 so on. This plugin provides all the basic features for editing or modifing such
 specfile.