Re: [Valgrind-users] Valgrind not working properly on imx6 platform

On 09/07/2017 Kacper Kowalski wrote: Thank you very much, John Reiser, for such extensive help. You're welcome. If I understood correctly, memcheck uses hardcoded SP and it's r13? It should use the register passed with ldmdb instruction as SP (within this example it will be r11)? No, the

Re: [Valgrind-users] Valgrind not working properly on imx6 platform

Thank you very much, John Reiser, for such extensive help. If I understood correctly, memcheck uses hardcoded SP and it's r13? It should use the register passed with ldmdb instruction as SP (within this example it will be r11)? According to your suggestion I used "--ignore-range-below-sp=X-Y", bu

Re: [Valgrind-users] Valgrind not working properly on imx6 platform

memcheck's bug is reporting the location "at 0x..." using the new value that was loaded into pc, instead of the original value of the pc of the instruction which suffered the complaint. https://bugs.kde.org/show_bug.cgi?id=384442 "ARM: bad pc in complaint if instruction changes pc" --

Re: [Valgrind-users] Valgrind not working properly on imx6 platform

cat /proc/cpuinfo [[snip]] processor: 1 model name: ARMv7 Processor rev 10 (v7l) BogoMIPS: 132.00 Features: half thumb fastmult vfp edsp neon vfpv3 tls vfpd32 CPU implementer: 0x41 CPU architecture: 7 CPU variant: 0x2 CPU part: 0xc09 CPU revision: 10 Hardware

Re: [Valgrind-users] Valgrind not working properly on imx6 platform

I booted from new image which was compiled fully with GCC-5.3 and the problem still occurs. The advantage is that packages with debug symbols were used and I can use the bt gdb command. GDB: (gdb) set verbose on (gdb) target remote | /usr/lib/valgrind/../../bin/vgdb --pid=8269 Remote debugging usi

Re: [Valgrind-users] Valgrind not working properly on imx6 platform

Openwrt does not have lscpu command available (nor in any package). cat /proc/cpuinfo processor: 0 model name: ARMv7 Processor rev 10 (v7l) BogoMIPS: 132.00 Features: half thumb fastmult vfp edsp neon vfpv3 tls vfpd32 CPU implementer: 0x41 CPU architecture: 7 CPU variant: 0

Re: [Valgrind-users] Valgrind not working properly on imx6 platform

> 1. > ==4996== Invalid read of size 4 > ==4996==at 0x40054EC: ??? (in /lib/ld-uClibc-0.9.33.2.so ) > ==4996== Address 0x7dbb6664 is on thread 1's stack > ==4996== 20 bytes below stack pointer GDB: 1. (gdb) info reg r0 0x400714867137864 r1

Re: [Valgrind-users] Valgrind not working properly on imx6 platform

Ok. Sorry, I overlooked it GDB: 1. (gdb) info reg r0 0x400714867137864 r1 0x00 r2 0x49ba00077307904 r3 0x49bd90c77322508 r4 0x4015f7867198840 r5 0x400605467133524 r6 0xa10 r7

Re: [Valgrind-users] Valgrind not working properly on imx6 platform

From valgrind(memcheck): ==2418== Invalid read of size 4 ==2418==at 0x40054EC: ??? (in /lib/ld-uClibc-0.9.33.2.so) ==2418== Address 0x7d87a664 is on thread 1's stack ==2418== 20 bytes below stack pointer Program received signal SIGTRAP, Trace/breakpoint trap. 0x040054ec in ?? (

Re: [Valgrind-users] Valgrind not working properly on imx6 platform

John Reiser 17:27 (18 godzin temu) > ==19124== at 0x40054EC: ??? (in /lib/ld-uClibc-0.9.33.2.so < http://ld-uClib... Kacper Kowalski 11:57 (1 minutę temu) do John Hi! By default valgrind is not selectable in menuconfig for IMX6 platform when cross compiling for Openwrt, but this platform is ba

Re: [Valgrind-users] Valgrind not working properly on imx6 platform

By default valgrind is not selectable in menuconfig for IMX6 platform when cross compiling for Openwrt, but this platform is based on ARM Cortex A9 core which is implementing ARMv7 architecture. This architecture is supported by valgrind, so I made little changes in Makefile of valgrind package to