Update Ubuntu 14.04 with full Valgrind LE support.

Bug #1386524 reported by bugproxy
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
valgrind (Ubuntu)
Trusty
Fix Released
Medium
Unassigned
Vivid
Fix Released
Medium
Unassigned

Bug Description

Problem Description

============================

Valgrind in Ubuntu 14.04 only has the needed bit to compile. It is not functional and crashes when used.

The Ubuntu 14.04 includes the Valgrind tool using a snap shot of the Valgrind SVN repository from April 11, 2014. The snap shot is the Valgrind 3.9 release and an IBM patch allow the Valgrind tool to compile for PPC64 little endian. However, the needed functional changes did not go into the Valgrind SVN repository until early August 2014. The latest Valgrind release came out in early September 2014.

We request that the next incremental release of Ubuntu 14.04 move to the Valgrind 3.10 release with the full PPC64 little endian support.

---uname output---

Segmentation fault (core dumped)

Machine Type = Power 8 LE

Steps to Reproduce

==========================

1) valgrind - to invoke the tool and it crashes

Userspace tool common name: Valgrind

The userspace tool has the following bit modes: 64-bit

Userspace tool obtained from project website: http://valgrind.org/

bugproxy (bugproxy)
tags: added: architecture-ppc64le bugnameltc-118068 severity-medium targetmilestone-inin---
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1386524/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
affects: ubuntu → valgrind (Ubuntu)
Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2015-07-14 21:12 EDT-------
On at 14.04.2 LTS install;

local experimentation has confirmed that valgrind segfaults when built out of the tools. (apt-get -b source valgrind)

But does seem to work OK when built directly from those same sources. Thus i suspect a subtle build option variation somewhere in the tooling.

version for reference:
16:11:06 0 willschm@genoa:~> apt-get -b source valgrind
<...>
Skipping already downloaded file 'valgrind_3.10~20140411-0ubuntu1.dsc'
Skipping already downloaded file 'valgrind_3.10~20140411.orig.tar.gz'
Skipping already downloaded file 'valgrind_3.10~20140411-0ubuntu1.debian.tar.gz'

Revision history for this message
Matthias Klose (doko) wrote :

confirmed, and there are other ppc64el issues like bug #1377796 too. I think we should just build the package from utopic/vivid to trusty.

Changed in valgrind (Ubuntu Trusty):
importance: Undecided → Medium
status: New → Confirmed
no longer affects: valgrind (Ubuntu)
Revision history for this message
Chris J Arges (arges) wrote :

Is this also going to be backported to vivid,utopic before trusty?

Revision history for this message
Brian Murray (brian-murray) wrote :

Utopic reaches end of life next week so that release isn't really relevant.

Revision history for this message
Chris J Arges (arges) wrote :

Still no upload for Vivid yet. Need that before we backport Wily into Trusty.

Revision history for this message
Adam Conrad (adconrad) wrote :

We need a test plan to validate this once it goes in. A 5MB diff is obviously unauditable, so some extra testing needs to be done to make sure bumping the version doesn't hurt anything. From IRC:

16:29 < infinity> doko: At least, a PPA test of $(reverse-depends -r trusty -b src:valgrind) should be done, and we also need some what to know that $(reverse-depends -r trusty src:valgrind) don't break.

Revision history for this message
Matthias Klose (doko) wrote :

built all reverse build dependencies of valgrind in the ubuntu-toolchain-r/ppa PPA:

summary: everything builds fine in main, and some issues in universe are unrelated to the valgrind upload. Please note that I will remove the packages from the PPA once the SRU is accepted.

abiword
alleyoop
digikam
diod
gsasl
gss
hud
indicator-network
indicator-network-prompt
jq
libdbusmenu
libdrm
libtest-valgrind-perl
libusermetrics
qpid-cpp
shishi
unity-voice
valkyrie
wine1.6
xserver-xorg-video-intel
xserver-xorg-video-intel-lts-utopic
xserver-xorg-video-intel-lts-vivid
        all ok

mir
        ftbfs on arm64 in trusty as well
mpich
        TODO: ftbfs on armhf (universe), however openmpi is the default
pypy
        ftbfs on amd64 i386, unrelated, filed SRU LP: #1499957.
rhmessaging
        missing b-d qpid-tools, universe, open issue
simgrid
        ftbfs on ppc64el (java archdir), no b-d on valgrind on ppc64el
starpu
        ftbfs on arm64 and ppc64el in trusty as well
swi-prolog
        ftbfs on ppc64el (java archdir)
xorg-gtest
        ftbfs with the existing valgrind as well

Revision history for this message
Chris J Arges (arges) wrote : Please test proposed package

Hello bugproxy, or anyone else affected,

Accepted valgrind into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/valgrind/1:3.10.1-1ubuntu3~14.04 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in valgrind (Ubuntu Trusty):
status: Confirmed → Fix Committed
tags: added: verification-needed
Revision history for this message
Chris J Arges (arges) wrote :

Hello bugproxy, or anyone else affected,

Accepted valgrind into vivid-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/valgrind/1:3.10.1-1ubuntu3~15.04 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in valgrind (Ubuntu Vivid):
status: New → Fix Committed
bugproxy (bugproxy)
tags: removed: verification-needed
tags: added: verification-needed
Carl Love (carll)
tags: added: verification-done
removed: architecture-ppc64le bot-comment bugnameltc-118068 severity-medium targetmilestone-inin--- verification-needed
bugproxy (bugproxy)
tags: added: architecture-ppc64le bugnameltc-118068 severity-medium targetmilestone-inin14043
removed: verification-done
tags: added: verification-needed
description: updated
tags: added: verification-done
removed: verification-needed
Revision history for this message
CDE Administration (cdeadmin) wrote :

test

Revision history for this message
Brian Murray (brian-murray) wrote :

Could somebody add some information describing how verification was done?

Revision history for this message
CDE Administration (cdeadmin) wrote :

check if this bug can be caught by bridge per IT129946 submitted by Chavez, pls ignore this comment.

Mathew Hodson (mhodson)
Changed in valgrind (Ubuntu Vivid):
importance: Undecided → Medium
Revision history for this message
Launchpad Janitor (janitor) wrote :

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 <email address hidden> Wed, 15 Jul 2015 09:37:42 +0200

Changed in valgrind (Ubuntu Trusty):
status: Fix Committed → Fix Released
Revision history for this message
Chris J Arges (arges) wrote : Update Released

The verification of the Stable Release Update for valgrind has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

---------------
valgrind (1:3.10.1-1ubuntu3~15.04) vivid-proposed; urgency=medium

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

 -- Matthias Klose <email address hidden> Sat, 26 Sep 2015 08:57:45 +0200

Changed in valgrind (Ubuntu Vivid):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.