[Bug 1435261] Re: valgrind packages ouf of sync with current glibc version (2.21)

Launchpad Bug Tracker 1435261 at bugs.launchpad.net
Wed Dec 2 18:37:45 UTC 2015


This bug was fixed in the package valgrind - 1:3.10.1-1ubuntu3~14.04

---------------
valgrind (1:3.10.1-1ubuntu3~14.04) trusty-proposed; urgency=medium

  * SRU. Backport the 1.10 series to 14.04 for ppc64el support. LP: #1386524.
  * Also fixes segfault on ppc64el, LP: #1377796.

valgrind (1:3.10.1-1ubuntu3) wily; urgency=medium

  * Build with GCC fixing PR target/65456. LP: #1434222.
  * Fix DCACHEBSIZE and HWCAP2 issues. LP: #1428002.
  * Fix bash command completion to respect end of options argument (--).
    LP: #840467.

valgrind (1:3.10.1-1ubuntu2) vivid; urgency=medium

  * Build for glibc-2.21. LP: #1435261.

valgrind (1:3.10.1-1ubuntu1) vivid; urgency=medium

  * Merge with Debian; remaining changes:
    - Remove valgrind-mpi package from Ubuntu and any references to it, as
      mpi-default-dev is in universe for the time being.
    - Lower over-inflated valgrind-dbg Recommends to Suggests instead.
    - Don't strip vgpreload* on ARM; this results in unusable stack traces
      without valgrind-dbg.
    - Configure with --enable-only64bit on AArch64.

 -- Matthias Klose <doko at ubuntu.com>  Wed, 15 Jul 2015 09:37:42 +0200

** Changed in: valgrind (Ubuntu Trusty)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to valgrind in Ubuntu.
https://bugs.launchpad.net/bugs/1435261

Title:
  valgrind packages ouf of sync with current glibc version (2.21)

Status in valgrind package in Ubuntu:
  Fix Released
Status in valgrind source package in Trusty:
  Fix Released

Bug description:
  The current version of valgrind (1:3.10.1-1ubuntu1) was built against
  version 2.19 of glibc, so its default suppression files target glibc
  libraries of that version.

  Valgrind needs to be updated and rebuilt to support the new version of
  glibc (2.21) in vivid.

  Also see bug #1284653, which describes the same problem for the
  transition from glibc 2.18 to 2.19.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/1435261/+subscriptions



More information about the foundations-bugs mailing list