2007-01-16 00:40:26 +01:00
|
|
|
#
|
2009-09-08 22:35:32 +02:00
|
|
|
# spec file for package valgrind (Version 3.5.0)
|
2007-01-16 00:40:26 +01:00
|
|
|
#
|
2010-01-07 13:04:11 +01:00
|
|
|
# Copyright (c) 2010 SUSE LINUX Products GmbH, Nuernberg, Germany.
|
2007-01-16 00:40:26 +01:00
|
|
|
#
|
2008-11-07 15:52:12 +01:00
|
|
|
# All modifications and additions to the file contributed by third parties
|
|
|
|
|
# remain the property of their copyright owners, unless otherwise agreed
|
|
|
|
|
# upon. The license for this file, and modifications and additions to the
|
|
|
|
|
# file, is the same license as for the pristine package itself (unless the
|
|
|
|
|
# license for the pristine package is not an Open Source License, in which
|
|
|
|
|
# case the license is the MIT License). An "Open Source License" is a
|
|
|
|
|
# license that conforms to the Open Source Definition (Version 1.9)
|
|
|
|
|
# published by the Open Source Initiative.
|
|
|
|
|
|
2007-01-16 00:40:26 +01:00
|
|
|
# Please submit bugfixes or comments via http://bugs.opensuse.org/
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
|
2008-04-28 02:03:35 +02:00
|
|
|
|
2007-01-16 00:40:26 +01:00
|
|
|
Name: valgrind
|
- update to 3.6.0 snapshot:
- Valgrind runs much faster when the --smc-check=all option is given.
- Cachegrind has a new processing script, cg_diff, which finds the
difference between two profiles. It's very useful for evaluating the
performance effects of a change in a program.
Related to this change, the meaning of cg_annotate's (rarely-used)
--threshold option has changed; this is unlikely to affect many people, if
you do use it please see the user manual for details.
- Callgrind now can do branch prediction simulation, similar to Cachegrind.
In addition, it optionally can count the number of executed global bus events.
Both can be used for a better approximation of a "Cycle Estimation" as
derived event (you need to update the event formula in KCachegrind yourself).
- Cachegrind and Callgrind now refer to the LL (last-level) cache rather
than the L2 cache. This is to accommodate machines with three levels of
caches -- if Cachegrind/Callgrind auto-detects the cache configuration of
such a machine it will run the simulation as if the L2 cache isn't
present. This means the results are less likely to match the true result
for the machine, but Cachegrind/Callgrind's results are already only
approximate, and should not be considered authoritative. The results are
still useful for giving a general idea about a program's locality.
- Massif has a new option, --pages-as-heap, which is disabled by default.
When enabled, instead of tracking allocations at the level of heap blocks
(as allocated with malloc/new/new[]), it instead tracks memory allocations
at the level of memory pages (as mapped by mmap, brk, etc). Each mapped
page is treated as its own block. Interpreting the page-level output is
harder than the heap-level output, but this option is useful if you want
to account for every byte of memory used by a program.
- Added new memcheck command-line option --show-possibly-lost.
OBS-URL: https://build.opensuse.org/package/show/devel:tools/valgrind?expand=0&rev=17
2010-10-13 13:43:20 +02:00
|
|
|
BuildRequires: gcc-c++ glibc-devel-32bit xorg-x11-devel docbook-xsl-stylesheets docbook_4 libxslt
|
2007-09-12 16:49:23 +02:00
|
|
|
%ifarch x86_64 ppc64
|
2007-01-23 15:15:03 +01:00
|
|
|
BuildRequires: gcc-32bit
|
2007-01-16 00:40:26 +01:00
|
|
|
%endif
|
2007-09-14 16:28:27 +02:00
|
|
|
Url: http://valgrind.org/
|
2010-01-07 13:04:11 +01:00
|
|
|
License: GPLv2
|
2007-01-16 00:40:26 +01:00
|
|
|
Group: Development/Tools/Debuggers
|
2007-09-14 16:28:27 +02:00
|
|
|
Summary: Valgrind Suite of Tools for Debugging and Profiling
|
2007-01-16 00:40:26 +01:00
|
|
|
BuildRoot: %{_tmppath}/%{name}-%{version}-build
|
- update to 3.6.0 snapshot:
- Valgrind runs much faster when the --smc-check=all option is given.
- Cachegrind has a new processing script, cg_diff, which finds the
difference between two profiles. It's very useful for evaluating the
performance effects of a change in a program.
Related to this change, the meaning of cg_annotate's (rarely-used)
--threshold option has changed; this is unlikely to affect many people, if
you do use it please see the user manual for details.
- Callgrind now can do branch prediction simulation, similar to Cachegrind.
In addition, it optionally can count the number of executed global bus events.
Both can be used for a better approximation of a "Cycle Estimation" as
derived event (you need to update the event formula in KCachegrind yourself).
- Cachegrind and Callgrind now refer to the LL (last-level) cache rather
than the L2 cache. This is to accommodate machines with three levels of
caches -- if Cachegrind/Callgrind auto-detects the cache configuration of
such a machine it will run the simulation as if the L2 cache isn't
present. This means the results are less likely to match the true result
for the machine, but Cachegrind/Callgrind's results are already only
approximate, and should not be considered authoritative. The results are
still useful for giving a general idea about a program's locality.
- Massif has a new option, --pages-as-heap, which is disabled by default.
When enabled, instead of tracking allocations at the level of heap blocks
(as allocated with malloc/new/new[]), it instead tracks memory allocations
at the level of memory pages (as mapped by mmap, brk, etc). Each mapped
page is treated as its own block. Interpreting the page-level output is
harder than the heap-level output, but this option is useful if you want
to account for every byte of memory used by a program.
- Added new memcheck command-line option --show-possibly-lost.
OBS-URL: https://build.opensuse.org/package/show/devel:tools/valgrind?expand=0&rev=17
2010-10-13 13:43:20 +02:00
|
|
|
Version: 3.5.90.svn11414
|
|
|
|
|
Release: 1
|
2007-12-12 21:29:12 +01:00
|
|
|
Source0: %{name}-%{version}.tar.bz2
|
2010-09-23 13:16:38 +02:00
|
|
|
# svn di svn://svn.valgrind.org/valgrind/tags/VALGRIND_3_5_0 svn://svn.valgrind.org/valgrind/branches/VALGRIND_3_5_BRANCH > 3_5_BRANCH.diff
|
|
|
|
|
# svn di svn://svn.valgrind.org/vex/tags/VEX_3_5_0 svn://svn.valgrind.org/vex/branches/VEX_3_5_BRANCH > VEX_3_5_BRANCH.diff
|
2010-01-07 13:04:11 +01:00
|
|
|
Patch1: jit-register-unregister.diff
|
2009-09-08 22:35:32 +02:00
|
|
|
Patch2: deprecated.diff
|
2010-10-13 14:10:18 +02:00
|
|
|
Patch3: valgrind-3.5.90.svn11391-s390x-port.diff
|
2007-12-03 23:48:02 +01:00
|
|
|
Provides: callgrind = %version
|
|
|
|
|
Obsoletes: callgrind < %version
|
2010-10-13 14:10:18 +02:00
|
|
|
ExclusiveArch: %ix86 x86_64 ppc ppc64 s390x
|
2007-01-16 00:40:26 +01:00
|
|
|
|
|
|
|
|
%description
|
|
|
|
|
Valgrind checks all memory operations in an application, like read,
|
|
|
|
|
write, malloc, new, free, and delete. Valgrind can find uses of
|
|
|
|
|
uninitialized memory, access to already freed memory, overflows,
|
2007-09-14 16:28:27 +02:00
|
|
|
illegal heap operations, memory leaks, and any illegal
|
2007-01-16 00:40:26 +01:00
|
|
|
new/malloc/free/delete commands. Another program in the package is
|
2007-09-14 16:28:27 +02:00
|
|
|
"cachegrind," a profiler based on the valgrind engine. It is plugin
|
|
|
|
|
based and many different tools are available.
|
2007-01-16 00:40:26 +01:00
|
|
|
|
2007-09-14 16:28:27 +02:00
|
|
|
To use valgrind you should launch the application like normal with
|
|
|
|
|
debuginfo packages installed, for example:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
_memcheck --leak-check_
|
2007-01-16 00:40:26 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
More valgrind options can be listed via "valgrind --help". There is
|
|
|
|
|
also complete documentation in the /usr/share/doc/packages/valgrind/
|
|
|
|
|
directory. A debugged application runs slower and needs much more
|
2007-09-14 16:28:27 +02:00
|
|
|
memory, but is usually still usable.
|
2007-01-16 00:40:26 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-04-06 00:31:09 +02:00
|
|
|
Authors:
|
|
|
|
|
--------
|
|
|
|
|
Julian Seward <jseward@acm.org>
|
|
|
|
|
Cerion Armour-Brown
|
|
|
|
|
Jeremy Fitzhardinge
|
|
|
|
|
Tom Hughes
|
|
|
|
|
Nicholas Nethercote
|
|
|
|
|
Paul Mackerras
|
|
|
|
|
Dirk Mueller
|
|
|
|
|
Robert Walsh
|
|
|
|
|
|
|
|
|
|
%package devel
|
2010-01-07 13:04:11 +01:00
|
|
|
License: GPLv2+
|
2007-09-14 16:28:27 +02:00
|
|
|
Summary: Valgrind Suite of Tools for Debugging and Profiling
|
2007-04-06 00:31:09 +02:00
|
|
|
Group: Development/Tools/Debuggers
|
|
|
|
|
Requires: %name = %version
|
|
|
|
|
|
|
|
|
|
%description devel
|
|
|
|
|
Valgrind checks all memory operations in an application, like read,
|
|
|
|
|
write, malloc, new, free, and delete. Valgrind can find uses of
|
|
|
|
|
uninitialized memory, access to already freed memory, overflows,
|
2007-09-14 16:28:27 +02:00
|
|
|
illegal heap operations, memory leaks, and any illegal
|
2007-04-06 00:31:09 +02:00
|
|
|
new/malloc/free/delete commands. Another program in the package is
|
2007-09-14 16:28:27 +02:00
|
|
|
"cachegrind," a profiler based on the valgrind engine. It is plugin
|
|
|
|
|
based and many different tools are available.
|
|
|
|
|
|
|
|
|
|
To use valgrind you should launch the application like normal with
|
|
|
|
|
debuginfo packages installed, for example:
|
|
|
|
|
|
2007-04-06 00:31:09 +02:00
|
|
|
|
2007-09-14 16:28:27 +02:00
|
|
|
_memcheck --leak-check_
|
2007-04-06 00:31:09 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
More valgrind options can be listed via "valgrind --help". There is
|
|
|
|
|
also complete documentation in the /usr/share/doc/packages/valgrind/
|
|
|
|
|
directory. A debugged application runs slower and needs much more
|
2007-09-14 16:28:27 +02:00
|
|
|
memory, but is usually still usable.
|
2007-04-06 00:31:09 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-01-16 00:40:26 +01:00
|
|
|
Authors:
|
|
|
|
|
--------
|
|
|
|
|
Julian Seward <jseward@acm.org>
|
|
|
|
|
Cerion Armour-Brown
|
|
|
|
|
Jeremy Fitzhardinge
|
|
|
|
|
Tom Hughes
|
|
|
|
|
Nicholas Nethercote
|
|
|
|
|
Paul Mackerras
|
|
|
|
|
Dirk Mueller
|
|
|
|
|
Robert Walsh
|
|
|
|
|
|
|
|
|
|
%prep
|
2007-12-12 21:29:12 +01:00
|
|
|
%setup -q -n %{name}-%{version}
|
2007-01-16 00:40:26 +01:00
|
|
|
cd VEX
|
|
|
|
|
cd ..
|
2010-01-07 13:04:11 +01:00
|
|
|
%patch1
|
2010-10-13 14:10:18 +02:00
|
|
|
%ifarch s390x
|
|
|
|
|
%patch3
|
|
|
|
|
%endif
|
- update to 3.6.0 snapshot:
- Valgrind runs much faster when the --smc-check=all option is given.
- Cachegrind has a new processing script, cg_diff, which finds the
difference between two profiles. It's very useful for evaluating the
performance effects of a change in a program.
Related to this change, the meaning of cg_annotate's (rarely-used)
--threshold option has changed; this is unlikely to affect many people, if
you do use it please see the user manual for details.
- Callgrind now can do branch prediction simulation, similar to Cachegrind.
In addition, it optionally can count the number of executed global bus events.
Both can be used for a better approximation of a "Cycle Estimation" as
derived event (you need to update the event formula in KCachegrind yourself).
- Cachegrind and Callgrind now refer to the LL (last-level) cache rather
than the L2 cache. This is to accommodate machines with three levels of
caches -- if Cachegrind/Callgrind auto-detects the cache configuration of
such a machine it will run the simulation as if the L2 cache isn't
present. This means the results are less likely to match the true result
for the machine, but Cachegrind/Callgrind's results are already only
approximate, and should not be considered authoritative. The results are
still useful for giving a general idea about a program's locality.
- Massif has a new option, --pages-as-heap, which is disabled by default.
When enabled, instead of tracking allocations at the level of heap blocks
(as allocated with malloc/new/new[]), it instead tracks memory allocations
at the level of memory pages (as mapped by mmap, brk, etc). Each mapped
page is treated as its own block. Interpreting the page-level output is
harder than the heap-level output, but this option is useful if you want
to account for every byte of memory used by a program.
- Added new memcheck command-line option --show-possibly-lost.
OBS-URL: https://build.opensuse.org/package/show/devel:tools/valgrind?expand=0&rev=17
2010-10-13 13:43:20 +02:00
|
|
|
# probably no longer needed, kept around already for a long time (2010-10-12)
|
|
|
|
|
#%patch2
|
2007-01-16 00:40:26 +01:00
|
|
|
|
|
|
|
|
%build
|
|
|
|
|
export CFLAGS="$RPM_OPT_FLAGS"
|
|
|
|
|
export CXXFLAGS="$RPM_OPT_FLAGS"
|
|
|
|
|
autoreconf -fi
|
|
|
|
|
export GDB=/usr/bin/gdb
|
|
|
|
|
%configure
|
|
|
|
|
make %{?jobs:-j%jobs}
|
- update to 3.6.0 snapshot:
- Valgrind runs much faster when the --smc-check=all option is given.
- Cachegrind has a new processing script, cg_diff, which finds the
difference between two profiles. It's very useful for evaluating the
performance effects of a change in a program.
Related to this change, the meaning of cg_annotate's (rarely-used)
--threshold option has changed; this is unlikely to affect many people, if
you do use it please see the user manual for details.
- Callgrind now can do branch prediction simulation, similar to Cachegrind.
In addition, it optionally can count the number of executed global bus events.
Both can be used for a better approximation of a "Cycle Estimation" as
derived event (you need to update the event formula in KCachegrind yourself).
- Cachegrind and Callgrind now refer to the LL (last-level) cache rather
than the L2 cache. This is to accommodate machines with three levels of
caches -- if Cachegrind/Callgrind auto-detects the cache configuration of
such a machine it will run the simulation as if the L2 cache isn't
present. This means the results are less likely to match the true result
for the machine, but Cachegrind/Callgrind's results are already only
approximate, and should not be considered authoritative. The results are
still useful for giving a general idea about a program's locality.
- Massif has a new option, --pages-as-heap, which is disabled by default.
When enabled, instead of tracking allocations at the level of heap blocks
(as allocated with malloc/new/new[]), it instead tracks memory allocations
at the level of memory pages (as mapped by mmap, brk, etc). Each mapped
page is treated as its own block. Interpreting the page-level output is
harder than the heap-level output, but this option is useful if you want
to account for every byte of memory used by a program.
- Added new memcheck command-line option --show-possibly-lost.
OBS-URL: https://build.opensuse.org/package/show/devel:tools/valgrind?expand=0&rev=17
2010-10-13 13:43:20 +02:00
|
|
|
pushd docs
|
|
|
|
|
#make all-docs
|
|
|
|
|
make FAQ.txt man-pages html-docs
|
|
|
|
|
popd
|
2007-01-16 00:40:26 +01:00
|
|
|
|
|
|
|
|
%install
|
|
|
|
|
make DESTDIR=$RPM_BUILD_ROOT install
|
|
|
|
|
mkdir -p $RPM_BUILD_ROOT/usr/share/doc/packages
|
|
|
|
|
mv $RPM_BUILD_ROOT/usr/share/doc/valgrind $RPM_BUILD_ROOT/usr/share/doc/packages
|
|
|
|
|
|
|
|
|
|
%files
|
|
|
|
|
%defattr(-,root,root)
|
2009-09-08 22:35:32 +02:00
|
|
|
%doc README* NEWS AUTHORS COPYING COPYING.DOCS
|
2007-01-16 00:40:26 +01:00
|
|
|
/usr/bin/*
|
|
|
|
|
%_libdir/valgrind
|
- update to 3.6.0 snapshot:
- Valgrind runs much faster when the --smc-check=all option is given.
- Cachegrind has a new processing script, cg_diff, which finds the
difference between two profiles. It's very useful for evaluating the
performance effects of a change in a program.
Related to this change, the meaning of cg_annotate's (rarely-used)
--threshold option has changed; this is unlikely to affect many people, if
you do use it please see the user manual for details.
- Callgrind now can do branch prediction simulation, similar to Cachegrind.
In addition, it optionally can count the number of executed global bus events.
Both can be used for a better approximation of a "Cycle Estimation" as
derived event (you need to update the event formula in KCachegrind yourself).
- Cachegrind and Callgrind now refer to the LL (last-level) cache rather
than the L2 cache. This is to accommodate machines with three levels of
caches -- if Cachegrind/Callgrind auto-detects the cache configuration of
such a machine it will run the simulation as if the L2 cache isn't
present. This means the results are less likely to match the true result
for the machine, but Cachegrind/Callgrind's results are already only
approximate, and should not be considered authoritative. The results are
still useful for giving a general idea about a program's locality.
- Massif has a new option, --pages-as-heap, which is disabled by default.
When enabled, instead of tracking allocations at the level of heap blocks
(as allocated with malloc/new/new[]), it instead tracks memory allocations
at the level of memory pages (as mapped by mmap, brk, etc). Each mapped
page is treated as its own block. Interpreting the page-level output is
harder than the heap-level output, but this option is useful if you want
to account for every byte of memory used by a program.
- Added new memcheck command-line option --show-possibly-lost.
OBS-URL: https://build.opensuse.org/package/show/devel:tools/valgrind?expand=0&rev=17
2010-10-13 13:43:20 +02:00
|
|
|
%doc %_mandir/*/*
|
2007-01-16 00:40:26 +01:00
|
|
|
|
2007-04-06 00:31:09 +02:00
|
|
|
%files devel
|
|
|
|
|
%defattr(-,root,root)
|
|
|
|
|
/usr/include/valgrind
|
|
|
|
|
/usr/%_lib/pkgconfig/valgrind.pc
|
|
|
|
|
|
2007-03-30 11:43:37 +02:00
|
|
|
%changelog
|
