Here is a copy of a crash I get when running valgrind on an ODROID-C2
(Cortex-A53).
==1028== Memcheck, a memory error detector
==1028== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==1028== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==1028== Command: python grc_tests/becdl.py
==1028==
==1028== Invalid read of size 4
==1028== at 0x48EC0D0: PyObject_Free (in /usr/lib/libpython2.7.so.1.0)
==1028== Address 0x4d0c020 is 224 bytes inside a block of size 2,731 free'd
==1028== at 0x484511C: free (in
/usr/lib/valgrind/vgpreload_memcheck-arm64-linux.so)
==1028== Block was alloc'd at
==1028== at 0x4843F84: malloc (in
/usr/lib/valgrind/vgpreload_memcheck-arm64-linux.so)
==1028==
==1028==
==1028== ---- Print suppression ? --- [Return/N/n/Y/y/C/c] ---- n
==1028== Conditional jump or move depends on uninitialised value(s)
==1028== at 0x48EC0DC: PyObject_Free (in /usr/lib/libpython2.7.so.1.0)
==1028==
==1028==
==1028== ---- Print suppression ? --- [Return/N/n/Y/y/C/c] ---- n
==1028== Use of uninitialised value of size 8
==1028== at 0x48EC108: PyObject_Free (in /usr/lib/libpython2.7.so.1.0)
==1028==
==1028==
==1028== ---- Print suppression ? --- [Return/N/n/Y/y/C/c] ---- n
==1028== Invalid read of size 4
==1028== at 0x48EC614: PyObject_Realloc (in /usr/lib/libpython2.7.so.1.0)
==1028== Address 0x4f96020 is 384 bytes inside a block of size 1,120 free'd
==1028== at 0x4846050: realloc (in
/usr/lib/valgrind/vgpreload_memcheck-arm64-linux.so)
==1028== Block was alloc'd at
==1028== at 0x4846050: realloc (in
/usr/lib/valgrind/vgpreload_memcheck-arm64-linux.so)
==1028==
==1028==
==1028== ---- Print suppression ? --- [Return/N/n/Y/y/C/c] ---- n
==1028== Conditional jump or move depends on uninitialised value(s)
==1028== at 0x48EC61C: PyObject_Realloc (in /usr/lib/libpython2.7.so.1.0)
==1028==
==1028==
==1028== ---- Print suppression ? --- [Return/N/n/Y/y/C/c] ---- n
ARM64 front end: load_store
disInstr(arm64): unhandled instruction 0x69410014
disInstr(arm64): 0110'1001 0100'0001 0000'0000 0001'0100
==1028== valgrind: Unrecognised instruction at address 0x5a32024.
==1028== at 0x5A32024: ??? (in
/usr/lib/python2.7/site-packages/PyQt4/QtCore.so)
==1028== Your program just tried to execute an instruction that Valgrind
==1028== did not recognise. There are two possible reasons for this.
==1028== 1. Your program has a bug and erroneously jumped to a non-code
==1028== location. If you are running Memcheck and you just saw a
==1028== warning about a bad jump, it's probably your program's fault.
==1028== 2. The instruction is legitimate but Valgrind doesn't handle it,
==1028== i.e. it's Valgrind's fault. If you think this is the case or
==1028== you are not sure, please let us know and we'll try to fix it.
==1028== Either way, Valgrind will now raise a SIGILL signal which will
==1028== probably kill your program.
==1028==
==1028== Process terminating with default action of signal 4 (SIGILL)
==1028== Illegal opcode at address 0x5A32024
==1028== at 0x5A32024: ??? (in
/usr/lib/python2.7/site-packages/PyQt4/QtCore.so)
==1028==
==1028== HEAP SUMMARY:
==1028== in use at exit: 2,729,906 bytes in 2,488 blocks
==1028== total heap usage: 12,592 allocs, 10,104 frees, 6,005,354 bytes
allocated
==1028==
==1028== 8,512 bytes in 14 blocks are possibly lost in loss record 2 of 5
==1028== at 0x4843F84: malloc (in
/usr/lib/valgrind/vgpreload_memcheck-arm64-linux.so)
==1028==
==1028==
==1028== ---- Print suppression ? --- [Return/N/n/Y/y/C/c] ----
W. Kyle Unice
Staff Engineer
MS F1H03
322 North 2200 West Dock 3
Salt Lake City, Utah 84116-0850
Voice: 801-594-2687
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users