https://bugs.kde.org/show_bug.cgi?id=487410
Bug ID: 487410
Summary: Valgrind is reporting Unhandled instruction at a
memory location on QNX OS
Classification: Developer tools
Product: valgrind
Version: 3.14.0
Platform: Other
OS: Unspecified
Status: REPORTED
Severity: crash
Priority: NOR
Component: memcheck
Assignee: jsew...@acm.org
Reporter: kant...@kpit.com
Target Milestone: ---
I am building the application on QNX and running those applications on R-CAR s4
board. Valgrind is integrated with my image. When I run the applications on the
target platform, I am facing the below issue.
==417838== Memcheck, a memory error detector
==417838== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==417838== Using Valgrind-3.14.0 and LibVEX; rerun with -h for copyright info
==417838== Command: ./bin/fusion
==417838==
ARM64 front end: load_store
disInstr(arm64): unhandled instruction 0x88E1FC02
disInstr(arm64): 1000'1000 1110'0001 1111'1100 0000'0010
==417838== valgrind: Unrecognised instruction at address 0x17e88.
==417838== at 0x17E88: ??? (in /proc/boot/ldqnx-64.so.2)
==417838== Your program just tried to execute an instruction that Valgrind
==417838== did not recognise. There are two possible reasons for this.
==417838== 1. Your program has a bug and erroneously jumped to a non-code
==417838== location. If you are running Memcheck and you just saw a
==417838== warning about a bad jump, it's probably your program's fault.
==417838== 2. The instruction is legitimate but Valgrind doesn't handle it,
==417838== i.e. it's Valgrind's fault. If you think this is the case or
==417838== you are not sure, please let us know and we'll try to fix it.
==417838== Either way, Valgrind will now raise a SIGILL signal which will
==417838== probably kill your program.
==417838==
==417838== Process terminating with default action of signal 4 (SIGILL):
dumping core
==417838== Illegal opcode at address 0x17E88
==417838== at 0x17E88: ??? (in /proc/boot/ldqnx-64.so.2)
==417838==
==417838== HEAP SUMMARY:
==417838== in use at exit: 0 bytes in 0 blocks
==417838== total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==417838==
==417838== All heap blocks were freed -- no leaks are possible
==417838==
==417838== For counts of detected and suppressed errors, rerun with: -v
==417838== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Illegal instruction
I am facing the same challenge with all the three commands mentioned below,
1. valgrind --tool=memcheck --leak-check=full ./app
2. valgrind --tool=memcheck
--show-leak-kinds=definite,indirect,possible --leak-check=full ./app
3. valgrind --log-file=cpu_burner.log --time-stamp=yes -v -v ./app
Looking for a solution on This.
Thank you !
--
You are receiving this mail because:
You are watching all bug changes.
