|
From: Murali K. <mur...@gm...> - 2017-05-26 08:48:18
|
Hi, As part of running the valgrind in our mips64 linux based system, we observed couple of issues. When tried to execute "ls" with valgrind, we see that the programme is getting crashed. More information about the valgrind programme are mentioned below. # file /usr/bin/valgrind /usr/bin/valgrind: ELF 64-bit MSB executable, MIPS, MIPS64 version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, not stripped # /usr/bin/valgrind --version valgrind-3.12.0 # valgrind --tool=memcheck ls ==28420== Memcheck, a memory error detector ==28420== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==28420== Using Valgrind-3.12.0 and LibVEX; rerun with -h for copyright info ==28420== Command: ls ==28420== Segmentation fault (core dumped) We tried to debug the crash file generated in the above case(by attaching to gdb) and observed that stack is corrupted(Valgrind binary has the debug symbols included). Every time when the crash is generated we observe that the stack is corrupted. gdb -c memcheck-mips64-SEGV.core /usr/bin/valgrind GNU gdb (GDB) 7.12.1 Copyright (C) 2017 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 "mips64-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...done. warning: core file may not match specified executable file. [New LWP 28420] Core was generated by `valgrind --tool=memcheck ls'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x000000ffee588570 in ?? () (gdb) bt #0 0x000000ffee588570 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) (gdb) quit We have also observed that below message is getting printed everytime with seperate crash files when attached to gdb. "warning: core file may not match specified executable file" I am not very sure whether this is a known issue in the current valgrind version or not. Could you please provide your inputs on the issue mentioned above. Thanks & Regards, Muralikrishna CH |