pool/valgrind
SHA256
2
0
Fork 1
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/valgrind?expand=0&rev=6

Browse Source
This commit is contained in:
OBS User unknown 2007-04-05 22:31:09 +00:00 committed by Git OBS Bridge
parent 6b2888c907
commit 8211b33f55
2 changed files with 53 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
valgrind.changes
View File

@ -1,3 +1,8 @@
-------------------------------------------------------------------
Thu Apr 5 16:09:51 CEST 2007 - dmueller@suse.de
- split into -devel subpackage
-------------------------------------------------------------------
Fri Mar 30 11:41:19 CEST 2007 - dmueller@suse.de

51
valgrind.spec
View File

@ -26,7 +26,7 @@ Group: Development/Tools/Debuggers
Summary: Memory Management Debugger
BuildRoot: %{_tmppath}/%{name}-%{version}-build
Version: 3.2.3
Release: 8
Release: 10
Source0: %{name}-%{version}.tar.bz2
# svn di svn://svn.valgrind.org/valgrind/tags/VALGRIND_3_2_1 svn://svn.valgrind.org/valgrind/branches/VALGRIND_3_2_BRANCH > 3_2_BRANCH.diff
# svn di svn://svn.valgrind.org/vex/tags/VEX_3_2_1 svn://svn.valgrind.org/vex/branches/VEX_3_2_BRANCH > VEX_3_2_BRANCH.diff
@ -60,6 +60,44 @@ but it has been successfully used to optimize several KDE applications.
Authors:
--------
Julian Seward <jseward@acm.org>
Cerion Armour-Brown
Jeremy Fitzhardinge
Tom Hughes
Nicholas Nethercote
Paul Mackerras
Dirk Mueller
Robert Walsh
%package devel
Summary: Memory Management Debugger
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,
illegal stack operations, memory leaks, and any illegal
new/malloc/free/delete commands. Another program in the package is
"cachegrind," a profiler based on the valgrind engine.
To use valgrind you should compile your application with "-g -O0"
compiler options. Afterwards you can use it with:
valgrind --tool=memcheck --sloppy-malloc=yes --leak-check=yes
--db-attach=yes my_application, for example.
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
memory, but is usually still usable. Valgrind is still in development,
but it has been successfully used to optimize several KDE applications.
Authors:
--------
Julian Seward <jseward@acm.org>
@ -96,14 +134,21 @@ mv $RPM_BUILD_ROOT/usr/share/doc/valgrind $RPM_BUILD_ROOT/usr/share/doc/packages
%files
%defattr(-,root,root)
%exclude %_libdir/valgrind/*/*.a
%doc README* NEWS ACKNOWLEDGEMENTS AUTHORS COPYING
/usr/bin/*
/usr/include/valgrind
/usr/%_lib/pkgconfig/valgrind.pc
%_libdir/valgrind
%doc %_mandir/*/*
%files devel
%defattr(-,root,root)
/usr/include/valgrind
/usr/%_lib/pkgconfig/valgrind.pc
%_libdir/valgrind/*/*.a
%changelog
* Thu Apr 05 2007 - dmueller@suse.de
- split into -devel subpackage
* Fri Mar 30 2007 - dmueller@suse.de
- add patch to track undefinedness in environment (#249676)
* Tue Jan 30 2007 - dmueller@suse.de