[Bug 1377796] Comment bridged from LTC Bugzilla
bugproxy
bugproxy at us.ibm.com
Thu Oct 8 16:10:46 UTC 2015
------- Comment From carll at us.ibm.com 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.
--
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/1377796
Title:
valgrind core dump rc 139 on ppc64le ubuntu 14.04
Status in valgrind package in Ubuntu:
Fix Released
Status in valgrind source package in Trusty:
Fix Committed
Status in valgrind source package in Vivid:
Fix Committed
Bug description:
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 at 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 at c656f2n07:~#
root at c656f2n07:~# valgrind
Segmentation fault (core dumped)
root at c656f2n07:~# valgrind --v
Segmentation fault (core dumped)
root at c656f2n07:~# valgrind --help
Segmentation fault (core dumped)
root at c656f2n07:~# valgrind -h
Segmentation fault (core dumped)
root at c656f2n07:~# echo $?
139
root at c656f2n07:~# valgrind
Segmentation fault (core dumped)
root at c656f2n07:~# echo $?
139
---uname output---
root at 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 <deshap at us.ibm.com> - ==
valgrind -d with console
---------------------------------------
root at 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 at c656f2n07:~#
-------
console:
-------
[437388.589266] memcheck-ppc64l[48585]: unhandled signal 11 at 3842fa403c40384c nip 3842fa403c40384c lr 0000000038087a70 code 30001
== Comment: #5 - Thierry Fauck <thierry.fauck at fr.ibm.com> - ==
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/1377796/+subscriptions
More information about the foundations-bugs
mailing list