https://bugs.kde.org/show_bug.cgi?id=340777
--- Comment #10 from Luiz Angelo De Luca <luizl...@gmail.com> --- The patch was already in use. See: https://github.com/lede-project/source/blob/lede-17.01/package/devel/valgrind/patches/200-musl_fix.patch I managed to compile a SVN version https://github.com/lede-project/source/compare/lede-project:lede-17.01...luizluca:cc/valgrind-svn?expand=1 But it changed nothing. At least, it would be easier to test SVN changes in the future. I also compiled valgrind with debug and used gdb. Inside gdb, I still see SIGILL (Illegal instruction), but running the program outside gdb seems to miss it. Maybe it is catched. Program received signal SIGILL, Illegal instruction. 0x38065bf0 in vgPlain_machine_get_hwcaps () at m_machine.c:1719 1719 have_DSPr2 = False; (gdb) cont Continuando. Program received signal SIGILL, Illegal instruction. 0x38065c34 in vgPlain_machine_get_hwcaps () at m_machine.c:1730 1730 have_DSP = False; (gdb) cont Continuando. warning: GDB can't find the start of the function at 0x42ae1d6c. GDB is unable to find the start of the function at 0x42ae1d6c 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 0x42ae1d6c 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. 0x42ae1d6c in ?? () Here is where I get the SIGSEGV. Maybe stack got corrupted. Is there any tips from here? -- You are receiving this mail because: You are watching all bug changes.
