https://bugs.kde.org/show_bug.cgi?id=365258
Bug ID: 365258
Summary: Reading syms from
/valgrind/lib/valgrind/memcheck-arm-linux bject
doesn't have a dynamic symbol table
Product: valgrind
Version: 3.11.0
Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: memcheck
Assignee: jsew...@acm.org
Reporter: rudici.caz...@litepoint.com
==1688== Memcheck, a memory error detector
==1688== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==1688== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==1688== Command: ./ltel1
==1688==
--1688-- Valgrind options:
--1688-- -v
--1688-- Contents of /proc/version:
--1688-- Linux version 3.0.51-rt75 (litepoint@rcazeao-o9020ub) (gcc version
4.5.1 (Sourcery G++ Lite 2010.09-50) ) #2 SMP P
REEMPT RT Wed May 25 14:41:22 PDT 2016
--1688--
--1688-- Arch and hwcaps: ARM, LittleEndian, ARMv7
--1688-- Page sizes: currently 4096, max supported 4096
--1688-- Valgrind library directory: /usr/sbin/valgrind/lib/valgrind
--1688-- Reading syms from /armlp/lte/fdd/phy/ltel1
--1688-- warning: DiCfSI 0x0 .. 0x3 outside mapped rx segments (NONE)
--1688-- warning: DiCfSI 0x0 .. 0x13 outside mapped rx segments (NONE)
--1688-- warning: DiCfSI 0x0 .. 0x13 outside mapped rx segments (NONE)
--1688-- warning: DiCfSI 0x0 .. 0x2f outside mapped rx segments (NONE)
--1688-- warning: DiCfSI 0x0 .. 0x7 outside mapped rx segments (NONE)
--1688-- warning: DiCfSI 0x8 .. 0x17 outside mapped rx segments (NONE)
--1688-- warning: DiCfSI 0x0 .. 0x7 outside mapped rx segments (NONE)
--1688-- warning: DiCfSI 0x8 .. 0x17 outside mapped rx segments (NONE)
--1688-- warning: DiCfSI 0x0 .. 0x7 outside mapped rx segments (NONE)
--1688-- warning: DiCfSI 0x8 .. 0x17 outside mapped rx segments (NONE)
--1688-- Reading syms from /lib/ld-2.11.1.so
--1688-- Reading syms from /usr/sbin/valgrind/lib/valgrind/memcheck-arm-linux
--1688-- object doesn't have a dynamic symbol table
--1688-- Scheduler: using generic scheduler lock implementation.
--1688-- Reading suppressions file:
/usr/sbin/valgrind/lib/valgrind/default.supp
==1688== embedded gdbserver: reading from
/tmp/vgdb-pipe-from-vgdb-to-1688-by-root-on-???
==1688== embedded gdbserver: writing to
/tmp/vgdb-pipe-to-vgdb-from-1688-by-root-on-???
==1688== embedded gdbserver: shared mem
/tmp/vgdb-pipe-shared-mem-vgdb-1688-by-root-on-???
==1688==
==1688== TO CONTROL THIS PROCESS USING vgdb (which you probably
==1688== don't want to do, unless you know exactly what you're doing,
==1688== or are doing some strange experiment):
==1688== /usr/sbin/valgrind/lib/valgrind/../../bin/vgdb --pid=1688
...command...
==1688==
==1688== TO DEBUG THIS PROCESS USING GDB: start GDB like this
==1688== /path/to/gdb ./ltel1
==1688== and then give GDB the following command
==1688== target remote | /usr/sbin/valgrind/lib/valgrind/../../bin/vgdb
--pid=1688
==1688== --pid is optional if only one valgrind process is running
==1688==
==1688==
==1688== Process terminating with default action of signal 4 (SIGILL): dumping
core
==1688== Illegal opcode at address 0x38086DFC
==1688== at 0x40007A0: ??? (in /lib/ld-2.11.1.so)
==1688==
==1688== HEAP SUMMARY:
==1688== in use at exit: 0 bytes in 0 blocks
==1688== total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==1688==
==1688== All heap blocks were freed -- no leaks are possible
==1688==
==1688== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
==1688== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Illegal instruction
Reproducible: Always
Steps to Reproduce:
1. Compile valgrind 3.11.0 source code
2. Comment out "add_hardwire_spec("ld-linux.so.3", "memcpy") in
coregrind/m_redir.c
3. Execute "valgrind -v ./app_name
Actual Results:
==1688== Process terminating with default action of signal 4 (SIGILL): dumping
core
==1688== Illegal opcode at address 0x38086DFC
==1688== at 0x40007A0: ??? (in /lib/ld-2.11.1.so
Expected Results:
I was expecting valgrind to detect memory leaks in app_name
--
You are receiving this mail because:
You are watching all bug changes.
