[Tizen-submit] 3967: New package devel:upstream/valgrind

noreply at tizen.org noreply at tizen.org
Fri May 3 23:43:04 GMT 2013


Hi,
Adding new package valgrind in project devel:upstream. Please review and accept ASAP.

Justification for this new package:

Submitter: Prajwal Mohan <prajwal.karur.mohan at intel.com>
Comments: submit/tizen/20130503.233445
Git project: platform/upstream/valgrind
Tag: submit/tizen/20130503.233445
Commit: 1707959 run autogen to check for glibc 2.17

Thank You,
Prajwal Mohan

[This message was auto-generated]

---

Request: #3967

  submit:       devel:upstream:build/valgrind(cleanup) -> devel:upstream


Message:
Submitter: Prajwal Mohan <prajwal.karur.mohan at intel.com>
Comments: submit/tizen/20130503.233445
Git project: platform/upstream/valgrind
Tag: submit/tizen/20130503.233445
Commit: 1707959 run autogen to check for glibc 2.17

State:   new        2013-05-03T16:02:48 tizenrobot
Comment: <no comment>
changes files:
--------------

++++++ new changes file:
--- valgrind.changes
+++ valgrind.changes
@@ -0,0 +1,10 @@
+* Mon Jan 14 2013 Anas Nashif <anas.nashif at intel.com> submit/trunk/20130115.033523 at a5b40ee
+- run autogen to check for glibc 2.17
+
+* Fri Jan 11 2013 Anas Nashif <anas.nashif at intel.com> accepted/trunk/20130111.201618 at ab0742f
+- make it build with glibc 2.17
+
+* Fri Jan 11 2013 Patrick McCarty <patrick.mccarty at linux.intel.com> upstream/3.8.1 at 68feca1
+- Add packaging for version 3.8.1
+- Imported Upstream version 3.8.1
+

new:
----
  valgrind-3.8.1.tar.bz2
  valgrind.changes
  valgrind.spec

spec files:
-----------

++++++ new spec file:
--- valgrind.spec
+++ valgrind.spec
@@ -0,0 +1,176 @@
+Name:           valgrind
+Url:            http://valgrind.org/
+Summary:        Memory Management Debugger
+License:        GPL-2.0+
+Group:          Development/Tools/Debuggers
+Version:        3.8.1
+Release:        0
+VCS:        platform/upstream/valgrind#submit/tizen/20130503.233445-0-g1707959
+Source0:        %{name}-%{version}.tar.bz2
+BuildRequires:  automake
+BuildRequires:  docbook-xsl-stylesheets
+BuildRequires:  docbook_4
+BuildRequires:  gcc-c++
+BuildRequires:  glibc-devel-32bit
+BuildRequires:  libxslt
+BuildRequires:  pkgconfig
+
+%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,
+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". 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.
+
+
+%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.

Please refer to OBS webUI for more details about this SR.


More information about the Tizen-submit mailing list