File: control

package info (click to toggle)
qprof 0.5.1-6
  • links: PTS
  • area: main
  • in suites: sarge
  • size: 1,652 kB
  • ctags: 307
  • sloc: sh: 8,446; ansic: 2,900; makefile: 123; csh: 2
file content (42 lines) | stat: -rw-r--r-- 2,060 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
Source: qprof
Section: devel
Priority: optional
Maintainer: Al Stone <ahs3@debian.org>
Build-Depends: debhelper (>= 4.0.0), libatomic-ops-dev, libunwind7-dev [ia64], libpfm2-dev [ia64], libpfm3-dev [ia64]
Standards-Version: 3.6.1

Package: qprof
Architecture: any
Suggests: oprofile, prospect, pfmon
Depends: ${shlibs:Depends} ${${Arch}:OtherDeps}
Description: Profiling utilities for Linux
 This is a set of profiling utilities, currently targeting only
 Linux. It includes a simple command line profiling tool, with the
 following characteristics:
    * It is intended to be easy to install and use. No kernel modules
    or changes are required for basic use. It can be used without root
    access.
    * It supports profiling of dynamically linked code and includes
    information on time spent in dynamic libraries.
    * It supports profiling of multithreaded applications.
    * It generates profiles for all subprocesses started from a
    shell. Thus it easily can be used to profile application with multiple
    processes.
    * It tries to generate symbolic output. This is usually successful
    for the main program, if that has debug information, i.e. was compiled
    with -g. If not, you may need a debugger to fully interpret the
    results. However the raw output will often give you a rough idea of
    where processor time is spent.
    * It currently generates "flat" profiles. The output tells you
    roughly how much time was spent in a given instruction, line, or
    function f. By default this does not include time spent in functions
    called by f, but on platforms supported by libunwind a possible
    alternative is to include callees in profile counts, thus recovering
    some gprof-like functionality.
    * Linux kernel functions are not profiled separately. By default,
    time spent in the kernel is credited to the library function which
    made the kernel call.
    * On Itanium, it can be used to generate hardware-event-based
    profiles. For example, it can tell you were most of the cache misses
    occur.