Menu
▾
▴
Re: [Valgrind-users] Valgrind crash on armv7l
|
From: <Fra...@we...> - 2017-01-04 12:43:24
|
Happy new year! Am 08.12.2016 14:34 schrieb John Reiser: > [...] > Most of the time? Then run valgrind under gdb, get the traceback > at the time of the SIGSEGV, and file a bug report against valgrind. > $ gdb valgrind > (gdb) run --tool=memcheck /path/to/the/smallest/program/which/fails > SIGSEGV > (gdb) bt > > It took some weeks until I found time to set things up, but now I have a backtrace with the actual valgrind version (please ignore the python errors, they exist only because of some mis-configuration of gdb build for the target) - see below. For me, this looks like there is an issue very early related to detection of the hardware architecture - any idea? best regards, Frank --------------------------------------------------------------------------- # gdb valgrind Python Exception <type 'exceptions.ImportError'> No module named gdb: gdb: warning: Could not load the Python gdb module from `/usr/share/gdb/python'. Limited Python support is available from the _gdb module. Suggest passing --data-directory=/path/to/gdb/data-directory. GNU gdb (GDB) 7.10.1 Copyright (C) 2015 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 "arm-buildroot-linux-gnueabihf". 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 valgrind...(no debugging symbols found)...done. (gdb) run --tool=memcheck /usr/bin/FanCtrl Starting program: /usr/bin/valgrind --tool=memcheck /usr/bin/FanCtrl Python Exception <type 'exceptions.NameError'> Installation error: gdb.execute_unwinders function is missing: Python Exception <type 'exceptions.NameError'> Installation error: gdb.execute_unwinders function is missing: Python Exception <type 'exceptions.NameError'> Installation error: gdb.execute_unwinders function is missing: Python Exception <type 'exceptions.NameError'> Installation error: gdb.execute_unwinders function is missing: Python Exception <type 'exceptions.NameError'> Installation error: gdb.execute_unwinders function is missing: process 401 is executing new program: /usr/lib/valgrind/memcheck-arm-linux Python Exception <type 'exceptions.NameError'> Installation error: gdb.execute_unwinders function is missing: Program received signal SIGILL, Illegal instruction. 0x38051308 in vgPlain_machine_get_hwcaps () at m_machine.c:1608 1608 m_machine.c: No such file or directory. (gdb) bt Python Exception <type 'exceptions.NameError'> Installation error: gdb.execute_unwinders function is missing: Python Exception <type 'exceptions.ImportError'> No module named gdb.frames: #0 0x38051308 in vgPlain_machine_get_hwcaps () at m_machine.c:1608 #1 0x380527d0 in valgrind_main (envp=0xbeff6ca4, argv=0xbeff6c94, argc=3) at m_main.c:1830 Python Exception <type 'exceptions.NameError'> Installation error: gdb.execute_unwinders function is missing: #2 _start_in_C_linux (pArgc=0xbeff6c90) at m_main.c:3407 #3 0x00000000 in ?? () Python Exception <type 'exceptions.NameError'> Installation error: gdb.execute_unwinders function is missing: Backtrace stopped: previous frame identical to this frame (corrupt stack?) |
