https://bugs.kde.org/show_bug.cgi?id=365208
Bug ID: 365208
Summary: valgrind stuck after redirecting "memcpy"
Product: valgrind
Version: unspecified
Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: memcheck
Assignee: jsew...@acm.org
Reporter: pwang...@gmail.com
valgrind 3.11.0 stuck after redirecting "memcpy" and does not start my
application. By using "top -H", I can see memcheck-ppc32- costs about 70% cpu.
==1404== Memcheck, a memory error detector
==1404== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==1404== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==1404== Command: /root/bin/bootenv /dev/mtd0
==1404==
--1404-- Valgrind options:
--1404-- -v
--1404-- Contents of /proc/version:
--1404-- Linux version 3.2.14 (pwang@ipsr-dev) (gcc version 4.6.4
(crosstool-NG crosstool-ng-1.22.0) ) #1 Fri Jun 10 15:19:58 EDT 2016
--1404--
--1404-- Arch and hwcaps: PPC32, BigEndian, ppc32-int-flt-GX
--1404-- Page sizes: currently 4096, max supported 65536
--1404-- Valgrind library directory: /usr/lib/valgrind
--1404-- Reading syms from /lib/ld-2.18.so
--1404-- Reading syms from /root/bin/bootenv
--1404-- object doesn't have a symbol table
--1404-- Reading syms from /usr/lib/valgrind/memcheck-ppc32-linux
--1404-- object doesn't have a symbol table
--1404-- object doesn't have a dynamic symbol table
--1404-- Scheduler: using generic scheduler lock implementation.
--1404-- Reading suppressions file: /usr/lib/valgrind/default.supp
==1404== embedded gdbserver: reading from
/tmp/vgdb-pipe-from-vgdb-to-1404-by-root-on-???
==1404== embedded gdbserver: writing to
/tmp/vgdb-pipe-to-vgdb-from-1404-by-root-on-???
==1404== embedded gdbserver: shared mem
/tmp/vgdb-pipe-shared-mem-vgdb-1404-by-root-on-???
==1404==
==1404== TO CONTROL THIS PROCESS USING vgdb (which you probably
==1404== don't want to do, unless you know exactly what you're doing,
==1404== or are doing some strange experiment):
==1404== /usr/lib/valgrind/../../bin/vgdb --pid=1404 ...command...
==1404==
==1404== TO DEBUG THIS PROCESS USING GDB: start GDB like this
==1404== /path/to/gdb /root/bin/bootenv
==1404== and then give GDB the following command
==1404== target remote | /usr/lib/valgrind/../../bin/vgdb --pid=1404
==1404== --pid is optional if only one valgrind process is running
==1404==
--1404-- REDIR: 0x401a248 (ld.so.1:strlen) redirected to 0x3806fc3c (???)
--1404-- REDIR: 0x401a080 (ld.so.1:strcmp) redirected to 0x3806fc64 (???)
--1404-- REDIR: 0x4019fa8 (ld.so.1:index) redirected to 0x3806fcd8 (???)
--1404-- Reading syms from /usr/lib/valgrind/vgpreload_core-ppc32-linux.so
--1404-- object doesn't have a symbol table
--1404-- Reading syms from /usr/lib/valgrind/vgpreload_memcheck-ppc32-linux.so
--1404-- object doesn't have a symbol table
--1404-- REDIR: 0x401ace4 (ld.so.1:mempcpy) redirected to 0xffbb644 (mempcpy)
Reproducible: Always
Steps to Reproduce:
1. Pick up any application on my Linux platform
2. type "valgrind -v myProgram"
Actual Results:
Valgrind stuck after outputting message below.
--1397-- REDIR: 0x401ace4 (ld.so.1:mempcpy) redirected to 0xffbb644 (mempcpy)
I am using buildroot 2016.02 for building kernel and all the applications
including valgrind 3.11.0
--
You are receiving this mail because:
You are watching all bug changes.
