|
From: Gnanasekar R <gna...@gm...> - 2012-05-25 07:04:14
|
Hi, I followed the instructions as mentioned in, https://bugs.kde.org/show_bug.cgi?id=276897#c0<val...@li...> to patch Valgrind 3.7.0 for armv5te and generated a build. I see that the memcheck keeps crashing, the moment I execute valgrind. With help of gdb I saw the instructions as below. Has anyone seen similar problem or am I missing anything? Please help! *(gdb) display /5i $pc 1: x/5i $pc => 0x38043130 <do_syscall_WRK+20>: pop {r4, r5, r7} 0x38043134 <do_syscall_WRK+24>: bx lr 0x38043138 <vgPlain_mk_SysRes_x86_linux>: add r3, r1, #4080 ; 0xff0 0x3804313c <vgPlain_mk_SysRes_x86_linux+4>: ldr r2, [pc, #32] ; 0x38043164 <vgPlain_mk_SysRes_x86_linux+44> 0x38043140 <vgPlain_mk_SysRes_x86_linux+8>: add r3, r3, #15 (gdb) * and this is the stack, *Program received signal SIGSEGV, Segmentation fault. 0x38043130 in do_syscall_WRK () (gdb) bt #0 0x38043130 in do_syscall_WRK () #1 0x380433e0 in vgPlain_do_syscall (sysno=<value optimized out>, a1=<value optimized out>, a2=<value optimized out>, a3=0, a4=0, a5=0, a6=0, a7=0, a8=0) at m_syscall.c:613 #2 0x380a91a0 in vgModuleLocal_am_open (pathname=<value optimized out>, flags=940216736, mode=<value optimized out>) at m_aspacemgr/aspacemgr-common.c:245 #3 0x3804edbc in read_procselfmaps_into_buf (record_mapping=0x380507d0 <read_maps_callback>, record_gap=0) at m_aspacemgr/aspacemgr-linux.c:3140 #4 parse_procselfmaps (record_mapping=0x380507d0 <read_maps_callback>, record_gap=0) at m_aspacemgr/aspacemgr-linux.c:3201 #5 0x38051254 in vgPlain_am_startup (sp_at_startup=<value optimized out>) at m_aspacemgr/aspacemgr-linux.c:1716 #6 0x38032ba8 in valgrind_main (argc=1, argv=0xbe8dde94, envp=0xbe8dde9c) at m_main.c:1525 #7 0x38037058 in _start_in_C_linux (pArgc=0xbe8dde90) at m_main.c:2785 * PS: Please let me know if this mail has to be posted to valgrind-dev-list as well. Thanks. |