[Tizen-submit] 34197: Changes to Tizen:IVI:Panda/valgrind

noreply at tizen.org noreply at tizen.org
Tue Mar 17 01:28:34 GMT 2015


Hi,
Chanho Park have made the following changes to valgrind in project Tizen:IVI:Panda. Please review and accept ASAP.

Thank You,

[This message was auto-generated]

---

Request: #34197

  submit:       Tizen:IVI:Panda:build/valgrind at 5(cleanup) -> Tizen:IVI:Panda


Message:
Submitter: Chanho Park <chanho61.park at samsung.com>
Comments: Bump to 3.10.1
Git project: platform/upstream/valgrind
Tag: submit/tizen/20150317.012701
Commit: 1394ad7c51c4ce5f64a91d73536a68e96c175998 configure.ac: Generalize glibc version check

State:   new        2015-03-17T01:28:11 tizenrobot
Comment: <no comment>
changes files:
--------------

++++++ new changes file:
--- _service:gbs:valgrind.changes
+++ _service:gbs:valgrind.changes
@@ -0,0 +1,10 @@
+* Mon Sep 15 2014 Chanho Park <chanho61.park at samsung.com> upstream/3.10.0-5-g292051f
+- Imported Upstream version 3.10.0
+
+* 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 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
+

++++++ deleted changes files:
--- valgrind.changes

old:
----
  0001-make-it-build-with-glibc-2.17.patch
  0002-make-it-build-with-glibc-2.18.patch
  0003-Fix-ptrace.h-error.-Changed-from-linux-ptrace.h-to-as.patch
  valgrind-3.8.1.tar.bz2
  valgrind.changes
  valgrind.manifest
  valgrind.spec

new:
----
  _service
  _service:gbs:0001-configure.ac-Generalize-gcc-clang-version-check.patch
  _service:gbs:0002-configure.ac-Generalize-glibc-version-check.patch
  _service:gbs:_git-meta
  _service:gbs:valgrind-3.10.1.tar.bz2
  _service:gbs:valgrind.changes
  _service:gbs:valgrind.manifest
  _service:gbs:valgrind.spec

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

++++++ new spec file:
--- _service:gbs:valgrind.spec
+++ _service:gbs:valgrind.spec
@@ -0,0 +1,200 @@
+Name:           valgrind
+VCS:            platform/upstream/valgrind#1394ad7c51c4ce5f64a91d73536a68e96c175998
+Url:            http://valgrind.org/
+Summary:        Memory Management Debugger
+License:        GPL-2.0+
+Group:          Development/Tools/Debuggers
+Version:        3.10.1
+Release:        0
+Source0:        %{name}-%{version}.tar.bz2
+Source1001: 	valgrind.manifest
+# Patches auto-generated by git-buildpackage:
+Patch0:         0001-configure.ac-Generalize-gcc-clang-version-check.patch
+Patch1:         0002-configure.ac-Generalize-glibc-version-check.patch
+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

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


More information about the Tizen-submit mailing list