Index index by Group index by Distribution index by Vendor index by creation date index by Name Mirrors Help Search

valgrind-devel-3.11.0-3.1 RPM for ppc64le

From OpenSuSE 42.2 updates for ppc64le

Name: valgrind-devel Distribution: openSUSE Leap 42.2
Version: 3.11.0 Vendor: openSUSE
Release: 3.1 Build date: Thu Jan 19 12:27:08 2017
Group: Development/Tools/Debuggers Build host: obs-power8-02
Size: 64031369 Source RPM: valgrind-3.11.0-3.1.src.rpm
Summary: Memory Management Debugger
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.






* Thu Jan 12 2017
  - Fix crash when running valgrind on programs linked with openssl
    library. Add vex-r3213.diff (bsc#1019536 kde#356393).
* Sat May 28 2016
  - add vex-r3197.diff (bsc#981447)
* Wed Apr 20 2016
  - The previous did not help, remove -strong first.
* Tue Apr 19 2016
  - also remove -fstack-protector-strong from the CFLAGS
* Fri Apr 01 2016
  - add r15702.diff, r15792.diff, vex-r3210.diff, r15802.diff (fate#319608)
* Mon Feb 22 2016
  - glibc-version.patch: removed, no longer needed
* Mon Feb 15 2016
  - update to 3.11.0 (fate#319608):
    * 3.11.0 is a feature release with many improvements and the usual
    collection of bug fixes.
  - replace gcc-version.patch with gcc5.patch: This is the upstream
  - drop valgrind-linux-4.0.patch: merged upstream
  - add svn-r15766.patch: Fix valgrind with recent kernels
  - jit-register-unregister.diff commented out, needs porting
* Thu Aug 06 2015
  - glibc-version.patch: Add support for glibc 2.22.
* Fri Apr 24 2015
  - Add valgrind-linux-4.0.patch: Fix build with linux kernel 4.0+.
    Taken from svn, rev 14955.
* Thu Apr 02 2015
  - Cleanup spec file with spec-cleaner
  - Update to 3.10.1
    * bugfix release (for full list of solved issues see NEWS file)
* Thu Feb 12 2015
  - gcc-version.patch: Add support for GCC 5.
* Mon Feb 09 2015
  - glibc-version.patch: Add support for glibc 2.21.
* Tue Sep 16 2014
  - glibc-2.19.patch: already upstream, so remove
  - Fix file list
* Tue Sep 16 2014
  - update to 3.10.0:
    * Support for the 64-bit ARM Architecture (AArch64 ARMv8).  This port
      is mostly complete, and is usable, but some SIMD instructions are as
      yet unsupported.
    * Support for little-endian variant of the 64-bit POWER architecture.
    * Support for Android on MIPS32.
    * Support for 64bit FPU on MIPS32 platforms.
    * Both 32- and 64-bit executables are supported on MacOSX 10.8 and 10.9.
    * Configuration for and running on Android targets has changed.
      See in the source tree for details.
    - drop VEX-r2803.diff, VEX-r2808.diff, VEX-r2816.diff, VEX-r2858.diff,
    VEX-r2904.diff, VEX-r2910.diff, VEX-r2914.diff, VEX-r2915.diff,
    VEX-r2916.diff, aarch64-VEX-support.diff, aarch64-support.diff,
    r13767.diff, r13770.diff, r14184.diff, r14238.diff, r14239.diff,
    r14240.diff, r14246.diff, r2798.diff, valgrind-r13948.diff
* Sun Aug 17 2014
  - update for ppc64le support (bnc#880334):
    - drop: valgrind-3.9.0-merge.patches.from.Paul.McKenney.patch,
    - add: VEX-r2803.diff, VEX-r2808.diff, VEX-r2816.diff
    VEX-r2904.diff, VEX-r2910.diff, VEX-r2914.diff, VEX-r2915.diff,
    VEX-r2916.diff, r13767.diff, r13770.diff, r14184.diff, r14238.diff,
    r14239.diff, r14240.diff, r14246.diff
* Sat Jul 26 2014
  - Fix patch conflicts.
* Wed Jun 18 2014
  - add VEX-r2858.diff, valgrind-r13948.diff for (bnc#883157)
* Sun May 18 2014
  - Update aarch64-support.diff, aarch64-VEX-support.diff from svn
* Thu Apr 24 2014
  - add aarch64-support.diff, aarch64-VEX-support.diff: aarch64 support
* Tue Feb 18 2014
  - added patches:
    * r2798.diff
* Tue Feb 11 2014
  - glibc-2.19.patch: add support for glibc 2.19
* Mon Jan 13 2014
  - add support of ppc64le architecture
  - added patches:
    * valgrind-3.9.0-merge.patches.from.Paul.McKenney.patch
    * valgrind-3.9.0-ppc64le-abiv2.patch
* Fri Jan 03 2014
  - add armv6-support.diff: Add support for armv6hl
* Wed Nov 06 2013
  - update to 3.9.0:
    * Support for Intel AVX2 instructions.  This is available only on 64
    bit code.
    * Support for POWER8 (Power ISA 2.07) instructions.
    * Initial support for Intel Transactional Synchronization Extensions,
    both RTM and HLE.
    * Initial support for Hardware Transactional Memory on POWER.
    * Improvements in handling of vectorised code, leading to
    significantly fewer false error reports.  You need to use the flag
    - -partial-loads-ok=yes to get the benefits of these changes.
    * Better control over the leak checker.  It is now possible to
    specify which leak kinds (definite/indirect/possible/reachable)
    should be displayed.
    * Reduced "possible leak" reports from the leak checker by the use
    of better heuristics.
    * Better control of stacktrace acquisition for heap-allocated
    * Better reporting of leak suppression usage.
    * New and modified GDB server monitor features.
    * New flag --sigill-diagnostics to control whether a diagnostic
    message is printed when the JIT encounters an instruction it can't
    * The maximum amount of memory that Valgrind can use on 64 bit
    targets has been increased from 32GB to 64GB.
    * Additional smaller new features and many bug fixes.
  - Remove obsolete raise-segnames-limit.diff,
    valgrind-glibc-2.17.patch and valgrind-glibc-2.18.patch.
* Tue Aug 13 2013
  - valgrind-glibc-2.18.patch: add support for glibc 2.18
* Fri Apr 05 2013
  - Add Source URL, see
* Mon Dec 31 2012
  - Fix last patch
* Mon Dec 31 2012
  - Add valgrind-glibc-2.17.patch to fix compilation with glibc 2.17
* Thu Oct 04 2012
  - raise seglimit to make it more useful for some apps
* Thu Sep 20 2012
  - update to 3.8.1 (bnc#776211):
    * Fixes some assertion failures.
    * Support for some missing instructions on ARM.
    * Support instructions MOVAPS and TZCNT.
    * Bug fixes.
* Wed Sep 05 2012
  - update to 3.8.0 (FATE#314090):
    * Support for MIPS32 platforms running Linux.  Valgrind has been
    tested on MIPS32 and MIPS32r2 platforms running different Debian
    Squeeze and MeeGo distributions.  Both little-endian and big-endian
    cores are supported.  The tools Memcheck, Massif and Lackey have
    been tested and are known to work. See README.mips for more details.
    * Preliminary support for Android running on x86.
    * Preliminary (as-yet largely unusable) support for MacOSX 10.8.
    * Support for Intel AVX instructions and for AES instructions.  This
    support is available only for 64 bit code.
    * Support for POWER Decimal Floating Point instructions.
    * Non-libc malloc implementations are now supported.  This is useful
    for tools that replace malloc (Memcheck, Massif, DRD, Helgrind).
    Using the new option --soname-synonyms, such tools can be informed
    that the malloc implementation is either linked statically into the
    executable, or is present in some other shared library different
    from  This makes it possible to process statically linked
    programs, and programs using other malloc libraries, for example
    TCMalloc or JEMalloc.
    * For tools that provide their own replacement for malloc et al, the
    option --redzone-size=<number> allows users to specify the size of
    the padding blocks (redzones) added before and after each client
    allocated block.  Smaller redzones decrease the memory needed by
    Valgrind.  Bigger redzones increase the chance to detect blocks
    overrun or underrun.  Prior to this change, the redzone size was
    hardwired to 16 bytes in Memcheck.
    * Memcheck:
    - The leak_check GDB server monitor command now can
      control the maximum nr of loss records to output.
    - Reduction of memory use for applications allocating
      many blocks and/or having many partially defined bytes.
    - Addition of GDB server monitor command 'block_list' that lists
      the addresses/sizes of the blocks of a leak search loss record.
    - Addition of GDB server monitor command 'who_points_at' that lists
      the locations pointing at a block.
    - If a redzone size > 0 is given, VALGRIND_MALLOCLIKE_BLOCK now will
      detect an invalid access of these redzones, by marking them
      noaccess.  Similarly, if a redzone size is given for a memory
      pool, VALGRIND_MEMPOOL_ALLOC will mark the redzones no access.
      This still allows to find some bugs if the user has forgotten to
      mark the pool superblock noaccess.
    - Performance of memory leak check has been improved, especially in
      cases where there are many leaked blocks and/or many suppression
      rules used to suppress leak reports.
    - Reduced noise (false positive) level on MacOSX 10.6/10.7, due to
      more precise analysis, which is important for LLVM/Clang
      generated code.  This is at the cost of somewhat reduced
      performance.  Note there is no change to analysis precision or
      costs on Linux targets.
    * DRD:
    - Added even more facilities that can help finding the cause of a data
      race, namely the command-line option --ptrace-addr and the macro
      DRD_STOP_TRACING_VAR(x). More information can be found in the manual.
    - Fixed a subtle bug that could cause false positive data race reports.
    * The C++ demangler has been updated so as to work well with C++
    compiled by up to at least g++ 4.6.
    * Tool developers can make replacement/wrapping more flexible thanks
    to the new option --soname-synonyms.  This was reported above, but
    in fact is very general and applies to all function
    replacement/wrapping, not just to malloc-family functions.
    * Round-robin scheduling of threads can be selected, using the new
    option --fair-sched= yes.  Prior to this change, the pipe-based
    thread serialisation mechanism (which is still the default) could
    give very unfair scheduling.  --fair-sched=yes improves
    responsiveness of interactive multithreaded applications, and
    improves repeatability of results from the thread checkers Helgrind
    and DRD.
    * For tool developers: support to run Valgrind on Valgrind has been
    improved.  We can now routinely Valgrind on Helgrind or Memcheck.
    * gdbserver now shows the float shadow registers as integer
    rather than float values, as the shadow values are mostly
    used as bit patterns.
    * Increased limit for the --num-callers command line flag to 500.
    * Performance improvements for error matching when there are many
    suppression records in use.
    * Improved support for DWARF4 debugging information (bug 284184).
    * Initial support for DWZ compressed Dwarf debug info.
    * Improved control over the IR optimiser's handling of the tradeoff
    between performance and precision of exceptions.  Specifically,
    - -vex-iropt-precise-memory-exns has been removed and replaced by
    - -vex-iropt-register-updates, with extended functionality.  This
    allows the Valgrind gdbserver to always show up to date register
    values to GDB.
    * Modest performance gains through the use of translation chaining for
    JIT-generated code.
* Fri Aug 17 2012
  - Support TZCNT/LZCNT instructions, generated by GCC 4.8,
    by falling back to BSF/BSR. (bnc#776211)
* Sun Jul 22 2012
  - Support glibc 2.16.
* Mon Jun 04 2012
  - arch is now armv7hl
* Tue May 15 2012
  - add "BuildRequires: pkgconfig" so the provides for
    "pkgconfig(valgrind)" gets created again
* Thu May 10 2012
  - Remove xorg-x11-devel BuildRequires: I can only guess it was
    there to make sure the xfree supp files are used, but they are
    used anyway by default. This helps resolve a build loop between
    libdrm and valgrind.
* Thu Apr 26 2012
  - Added patch valgrind-3.7.0-automake-1.11.2.patch to fix automake issue
    * See
* Thu Dec 29 2011
  - fix build against glibc 2.15
* Mon Dec 19 2011
  - build only on armv7l, not armv5
* Wed Nov 30 2011
  - add automake as buildrequire to avoid implicit dependency
* Wed Nov 09 2011
  - update to 3.7.0 (bnc#724215):
    * Support for IBM z/Architecture (s390x) running Linux.  Valgrind can
    analyse 64-bit programs running on z/Architecture.  Most user space
    instructions up to and including z10 are supported.
    See README.s390 for more details.
    * Support for the IBM Power ISA 2.06 (Power7 instructions)
    * Further solidification of support for SSE 4.2 in 64-bit mode
    * Memcheck:
    * - reduction of memory use in some circumstances
    * - improved handling of freed memory for finding more errors
    * - fix of a longstanding bug that could cause false negatives
    * Helgrind:
    * - Helgrind: performance improvements and major memory use reductions
    * GDB server: Valgrind now has an embedded GDB server.  That means it
    is possible to control a Valgrind run from GDB, doing all the usual
    things that GDB can do (single stepping, breakpoints, examining
    data, etc).  Tool-specific functionality is also available.
    * Over 160 bugs have been fixed.
* Mon Oct 24 2011
  - fix build on ppc (32bit)
* Sun Oct 02 2011
  - enable build on %%arm
* Fri Aug 19 2011
  - fix build against glibc 2.14
  - require the right version of glibc at runtime (part of fix for bnc#700362)
* Tue Jul 05 2011
  - Support Linux kernel 3.x (bnc#724215)
* Wed Jun 22 2011
  - fix merge error
* Sat Jun 18 2011
  - Improve Valgrind POWER6 and POWER7/P7 support (bnc#700358)
* Tue May 17 2011
  - revert removal for gcc-32bit requirement, breaks valgrinding
    32bit code on 64bit archs (bnc#705405)
* Mon Apr 11 2011
  - fix testsuite for s390 (kde#264800, kde#265762, kde#253206)
  - Add folding rules for Clz32 and Clz64 (kde#243404)
  - Refresh s390x port (kde#243404)
* Wed Mar 16 2011
  - update to 3.6.1 (bnc#679106):
    3.6.1 is a bug fix release.  It adds support for some SSE4
    instructions that were omitted in 3.6.0 due to lack of time.  Initial
    support for glibc-2.13 has been added.  A number of bugs causing
    crashing or assertion failures have been fixed.
* Fri Oct 22 2010
  - update to 3.6.0:
    3.6.0 is a feature release with many significant improvements and the
    usual collection of bug fixes. See the NEWS file for details.
* Thu Oct 21 2010
  - apparently gcc-32bit does not exist on old code streams, but
    it seems to work without it as well
* Wed Oct 20 2010
  - disable building docs until I find a way to build them without
    network access
* Wed Oct 13 2010
  - add s390x port (FATE#310036)
  - 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.
    - Support for analyzing programs running under Wine with has been improved.
      The header files <valgrind/valgrind.h>, <valgrind/memcheck.h> and
      <valgrind/drd.h> can now be used in Windows-programs compiled with MinGW
      or one of the Microsoft Visual Studio compilers.
    - DRD does now have two new command-line options: --free-is-write and
    - -trace-alloc. The former allows to detect reading from already freed
      memory, and the latter allows to trace all memory allocations and
    - Several new annotations have been added in DRD: custom barrier
      implementations can now be annotated and benign races on static variables
    - The happens before / happens after annotations in DRD have been made more
      powerful such that these can now also be used to annotate e.g. a smart
      pointer implementation.
* Thu Sep 23 2010
  - increase stack size (bnc#640793)
* Fri May 07 2010
  - fix build for ppc64
* Mon Apr 26 2010
  - handle pthread apps better (bnc#599585)
  - prefer CFI for better stack unwinding (bnc#559061)
* Fri Mar 26 2010
  - handle inotify_init1 (bnc#558964)
* Wed Jan 06 2010
  - fix build against glibc 2.11
* Wed Dec 02 2009
  - update and reenable jit-register-unregister.diff
* Tue Nov 03 2009
  - updated patches to apply with fuzz=0
* Tue Sep 08 2009
  - update to 3.5.0:
    * Support for glibc 2.10, gcc 4.5 has been added.
    * Improvements and simplifications to Memcheck's leak checker.
    * Clarification and simplifications in various aspects of Valgrind's
      text output.
    * XML output for Helgrind and Ptrcheck.
    * Performance and stability improvements for Helgrind and DRD.
    * Genuinely atomic support for x86/amd64/ppc atomic instructions.
    * A new experimental tool, BBV, useful for computer architecture
    * Improved Wine support, including ability to read Windows PDB
* Fri Mar 13 2009
  - update to 3.4.1 (bnc#479701):
    * 3.4.1 is a bug-fix release that fixes some regressions and
    assertion failures in debug info reading in 3.4.0, most notably
    incorrect stack traces on amd64-linux on older (glibc-2.3 based)
    systems. Various other debug info problems are also fixed. A
    number of bugs in the exp-ptrcheck tool introduced in 3.4.0
    have been fixed.



Generated by rpm2html 1.8.1

Fabrice Bellet, Wed Oct 10 02:37:35 2018