Bug#854194: valgrind segfaults on mipsel
Package: valgrind
Version: 1:3.12.0~svn20160714-1+b1
Severity: serious
Seen with both 1:3.12.0~svn20160714-1+b1 and 1:3.12.0-1.1:
(sid_mipsel-dchroot)bunk@eller:~$ valgrind /usr/bin/hello
==32333== Memcheck, a memory error detector
==32333== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==32333== Using Valgrind-3.12.0 and LibVEX; rerun with -h for copyright info
==32333== Command: /usr/bin/hello
==32333==
Segmentation fault
(sid_mipsel-dchroot)bunk@eller:~$ gdb /usr/bin/valgrind.bin
GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "mipsel-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/valgrind.bin...Reading symbols from /usr/lib/debug//usr/bin/valgrind.bin...done.
done.
(gdb) run /usr/bin/hello
Starting program: /usr/bin/valgrind.bin /usr/bin/hello
process 32540 is executing new program: /usr/lib/valgrind/memcheck-mips32-linux
==32540== Memcheck, a memory error detector
==32540== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==32540== Using Valgrind-3.12.0 and LibVEX; rerun with -h for copyright info
==32540== Command: /usr/bin/hello
==32540==
warning: GDB can't find the start of the function at 0x433a2f74.
GDB is unable to find the start of the function at 0x433a2f74
and thus can't determine the size of that function's stack frame.
This means that GDB may be unable to access that stack frame, or
the frames below it.
This problem is most likely caused by an invalid program counter or
stack pointer.
However, if you think GDB should simply search farther back
from 0x433a2f74 for code which looks like the beginning of a
function, you can increase the range of the search using the `set
heuristic-fence-post' command.
Program received signal SIGSEGV, Segmentation fault.
0x433a2f74 in ?? ()
(gdb)
Reply to: