valgrind core dump rc 139 on ppc64le ubuntu 14.04

[bugproxy]

Problem Description
=================
valgrind core dump rc 139 on ppc64le ubuntu 14.04

^^^^^^
BUILD:
^^^^^^
Ubuntu 14.04 LTS c656f2n07 hvc0
Linux c656f2n07 3.13.0-30-generic #54-Ubuntu SMP Mon Jun 9 22:46:02 UTC 2014 ppc
64le ppc64le ppc64le GNU/Linux

Steps to Reproduce
======================
1. run valgrind command.
2. watch it core dump

login to system. run any valgrind command. It coredumps

^^^^^^^^
SYMPTOM
^^^^^^^^
root@c656f2n07:~# uname -a
Linux c656f2n07 3.13.0-30-generic #55-Ubuntu SMP Fri Jul 4 21:29:58 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux
root@c656f2n07:~#
root@c656f2n07:~# valgrind
Segmentation fault (core dumped)
root@c656f2n07:~# valgrind --v
Segmentation fault (core dumped)
root@c656f2n07:~# valgrind --help
Segmentation fault (core dumped)
root@c656f2n07:~# valgrind -h
Segmentation fault (core dumped)
root@c656f2n07:~# echo $?
139
root@c656f2n07:~# valgrind
Segmentation fault (core dumped)
root@c656f2n07:~# echo $?
139

---uname output---
root@c656f2n07:~# uname -a Linux c656f2n07 3.13.0-30-generic #55-Ubuntu SMP Fri Jul 4 21:29:58 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux

---Additional Hardware Info---
IBM p8 Tuleta 22L model

 Machine Type = 8247-22L U8247.22L.211216A

== Comment: #4 - David E. Shapiro <email address hidden> - ==
valgrind -d with console
---------------------------------------
root@c656f2n07:~# valgrind -d
--48585:1:debuglog DebugLog system started by Stage 1, level 1 logging requested
--48585:1:launcher no tool requested, defaulting to 'memcheck'
--48585:1:launcher no client specified, defaulting platform to 'ppc64le-linux'
--48585:1:launcher launching /usr/lib/valgrind/memcheck-ppc64le-linux
Segmentation fault (core dumped)
root@c656f2n07:~#

-------
console:
-------
[437388.589266] memcheck-ppc64l[48585]: unhandled signal 11 at 3842fa403c40384c nip 3842fa403c40384c lr 0000000038087a70 code 30001

== Comment: #5 - Thierry Fauck <email address hidden> - ==
On trusty, pb still present
$ uname -a
Linux fauck3 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:50:31 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux

$ valgrind -d /bin/true
--10974:1:debuglog DebugLog system started by Stage 1, level 1 logging requested
--10974:1:launcher no tool requested, defaulting to 'memcheck'
--10974:1:launcher selected platform 'ppc64le-linux'
--10974:1:launcher launching /usr/lib/valgrind/memcheck-ppc64le-linux
Segmentation fault

On utopic it sounds there is no problem
$ valgrind -d /bin/true
--3305:1:debuglog DebugLog system started by Stage 1, level 1 logging requested
--3305:1:launcher no tool requested, defaulting to 'memcheck'
--3305:1:launcher selected platform 'ppc64le-linux'
--3305:1:launcher launching /usr/lib/valgrind/memcheck-ppc64le-linux
--3305:1:debuglog DebugLog system started by Stage 2 (main), level 1 logging requested
--3305:1:main Welcome to Valgrind version 3.10.0 debug logging
--3305:1:main Checking current stack is plausible
--3305:1:main Checking initial stack was noted
--3305:1:main Starting the address space manager
--3305:1:main Address space manager is running
--3305:1:main Starting the dynamic memory manager
--3305:1:mallocfr newSuperblock at 0x802010000 (pszB 4194272) owner VALGRIND/core
--3305:1:mallocfr deferred_reclaimSuperblock at 0x802010000 (pszB 4194272) (prev 0x0) owner VALGRIND/core
--3305:1:main Dynamic memory manager is running
--3305:1:main Initialise m_debuginfo
--3305:1:main VG_(libdir) = /usr/lib/valgrind
--3305:1:main Getting launcher's name ...
--3305:1:main ... /usr/bin/valgrind.bin
--3305:1:main Get hardware capabilities ...
--3305:1:machine dcbz_szB=128 dcbzl_szB=128
--3305:1:machine F 1 V 1 FX 1 GX 1 VX 1 DFP 1 ISA2.07 0
--3305:1:cache Could not autodetect cache info
--3305:1:main ... arch = PPC64, hwcaps = ppc64-int-flt-vmx-FX-GX-VX-DFP
--3305:1:main Getting the working directory at startup
--3305:1:main ... /home/ubuntu
--3305:1:main Split up command line
--3305:1:main (early_) Process Valgrind's command line options
--3305:1:main Create initial image
--3305:1:initimg Loading client
--3305:1:initimg Setup client env
--3305:1:initimg Setup client stack: size will be 8388608
--3305:1:initimg Setup client data (brk) segment
--3305:1:main Setup file descriptors
--3305:1:main Create fake /proc/<pid>/cmdline
--3305:1:main Create fake /proc/<pid>/auxv
--3305:1:main Initialise the tool part 1 (pre_clo_init)
--3305:1:mallocfr deferred_reclaimSuperblock NULL (prev 0x802010000) owner VALGRIND/core
--3305:1:mallocfr newSuperblock at 0x802410000 (pszB 4194272) owner VALGRIND/core
--3305:1:main Print help and quit, if requested
--3305:1:main (main_) Process Valgrind's command line options, setup loggin

[Ubuntu Foundations Team Bug Bot (crichton)]

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/1377796/+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.]

[Chris J Arges (arges)]

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!

[Chris J Arges (arges)]

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!

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2015-10-08 16:04 EDT-------
I went to the site listed in comment 9

https://launchpad.net/ubuntu/+source/valgrind/1:3.10.1-1ubuntu3~15.04

I then downloaded the three files to build the package and moved them to /tmp/Junk on my target ppc64le system running Ubuntu 14.10. I don't have access to an Ubuntu 14.04 system.

On the PPC64 le system I ran the command "dpkg-source -x *.dsc" to create the valgrind-3.10.1 source tree. I changed directories to the created valgrind-3.10.1 directory. I ran the following commands to build and test the package.

./autogen.sh
./configure --prefix=/tmp/Junk --build=powerpc64le-linux-gnu

make -j 5
make install
cd ../bin

./bin/valgrind ls
==24391== Memcheck, a memory error detector
==24391== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==24391== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info
==24391== Command: ls
==24391==
bin valgrind-3.10.1
include valgrind_3.10.1-1ubuntu3~15.04.debian.tar.gz
lib valgrind_3.10.1-1ubuntu3~15.04.dsc
share valgrind_3.10.1.orig.tar.bz2
==24391==
==24391== HEAP SUMMARY:
==24391== in use at exit: 21,123 bytes in 14 blocks
==24391== total heap usage: 49 allocs, 35 frees, 58,342 bytes allocated
==24391==
==24391== LEAK SUMMARY:
==24391== definitely lost: 0 bytes in 0 blocks
==24391== indirectly lost: 0 bytes in 0 blocks
==24391== possibly lost: 0 bytes in 0 blocks
==24391== still reachable: 21,123 bytes in 14 blocks
==24391== suppressed: 0 bytes in 0 blocks
==24391== Rerun with --leak-check=full to see details of leaked memory
==24391==
==24391== For counts of detected and suppressed errors, rerun with: -v
==24391== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

Valgrind appears to have compiled without error and runs a simple command without crashing.

The referenced package appears to have the needed fixes in it.

[Breno Leitão (breno-leitao)]

Carll,

Could you try to get the package from the -proposed archive?

[Breno Leitão (breno-leitao)]

On the -proposed archive, the package is already built and compiled...

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2015-10-21 15:31 EDT-------
I found the binary version of the updated package from the proposed archive.

https://launchpad.net/ubuntu/trusty/ppc64el/valgrind/1:3.10.1-1ubuntu3~14.04

I downloaded the binary file valgrind_3.10.1-1ubuntu3~14.04_ppc64el.deb (8.2 MiB) from the page. I installed the package, verified that the new version worked. Then deleted it, verified that it was gone and reinstalled and tested again just to verify that I was actually running the updated valgrind. OK, I am paranoid. The binary package runs fine on the basic tests that I tried. It all looks good to me.

[Launchpad Janitor (janitor)]

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

[Chris J Arges (arges)]

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.

[Launchpad Janitor (janitor)]

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