Hello community,
here is the log from the commit of package valgrind
checked in at Fri Apr 6 00:31:08 CEST 2007.
--------
--- valgrind/valgrind.changes 2007-03-30 11:41:35.000000000 +0200
+++ /mounts/work_src_done/STABLE/valgrind/valgrind.changes 2007-04-05 16:09:58.000000000 +0200
@@ -1,0 +2,5 @@
+Thu Apr 5 16:09:51 CEST 2007 - dmueller@suse.de
+
+- split into -devel subpackage
+
+-------------------------------------------------------------------
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ valgrind.spec ++++++
--- /var/tmp/diff_new_pack.g30936/_old 2007-04-06 00:30:58.000000000 +0200
+++ /var/tmp/diff_new_pack.g30936/_new 2007-04-06 00:30:58.000000000 +0200
@@ -26,7 +26,7 @@
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
@@ -71,6 +71,44 @@
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