https://bugs.kde.org/show_bug.cgi?id=340777
--- Comment #5 from Luiz Angelo De Luca <luizl...@gmail.com> --- Is it really necessary to test SVN? At least with 3.12.0, the problem remains: # valgrind ping 8.8.8.8 ==24067== Memcheck, a memory error detector ==24067== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==24067== Using Valgrind-3.12.0 and LibVEX; rerun with -h for copyright info ==24067== Command: ping 8.8.8.8 ==24067== ==24067== Conditional jump or move depends on uninitialised value(s) ==24067== at 0x40731E4: ??? (in /lib/libc.so) ==24067== by 0x4083164: ??? (in /lib/libc.so) ==24067== ==24067== Conditional jump or move depends on uninitialised value(s) ==24067== at 0x4072924: ??? (in /lib/libc.so) ==24067== by 0x4072D98: ??? (in /lib/libc.so) ==24067== vex mips->IR: unhandled instruction bytes: 0x41 0x67 0x25 0x22 ==24067== valgrind: Unrecognised instruction at address 0x4077b5. ==24067== at 0x4077B5: ??? (in /bin/busybox) ==24067== by 0x401E6A0: ??? (in /lib/libc.so) ==24067== Your program just tried to execute an instruction that Valgrind ==24067== did not recognise. There are two possible reasons for this. ==24067== 1. Your program has a bug and erroneously jumped to a non-code ==24067== location. If you are running Memcheck and you just saw a ==24067== warning about a bad jump, it's probably your program's fault. ==24067== 2. The instruction is legitimate but Valgrind doesn't handle it, ==24067== i.e. it's Valgrind's fault. If you think this is the case or ==24067== you are not sure, please let us know and we'll try to fix it. ==24067== Either way, Valgrind will now raise a SIGILL signal which will ==24067== probably kill your program. ==24067== ==24067== Process terminating with default action of signal 4 (SIGILL) ==24067== Illegal opcode at address 0x4077B5 ==24067== at 0x4077B5: ??? (in /bin/busybox) ==24067== by 0x401E6A0: ??? (in /lib/libc.so) ==24067== ==24067== HEAP SUMMARY: ==24067== in use at exit: 0 bytes in 0 blocks ==24067== total heap usage: 0 allocs, 0 frees, 0 bytes allocated ==24067== ==24067== All heap blocks were freed -- no leaks are possible ==24067== ==24067== For counts of detected and suppressed errors, rerun with: -v ==24067== Use --track-origins=yes to see where uninitialised values come from ==24067== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0) Illegal instruction If needed, I can recompile source from SVN with debuginfo -- You are receiving this mail because: You are watching all bug changes.
