Re: [Valgrind-users] Could valgrind run on Wind River 2.0 ?

2011-05-04 Thread Bart Van Assche
2011/5/4 liujianping > Could valgrind run on Wind River 2.0 ? (the sys on my arm board is Wind > River 2.0). > (Wind River 2.0 with kernel 2.6.21; gcc 4.1.2; glibc 2.5) > > I find the information on http://valgrind.org/info/ > "Valgrind runs on several popular platforms, such as x86/Linux, AMD64/

[Valgrind-users] Could valgrind run on Wind River 2.0 ?

2011-05-04 Thread liujianping
Hi, Could valgrind run on Wind River 2.0 ? (the sys on my arm board is Wind River 2.0). (Wind River 2.0 with kernel 2.6.21; gcc 4.1.2; glibc 2.5) I find the information onhttp://valgrind.org/info/ "Valgrind runs on several popular platforms, such as x86/Linux, AMD64/Linux and PPC32/Linux. Val

Re: [Valgrind-users] UME Error 22

2011-05-04 Thread John Reiser
> This is objdump of vgpreload_core-arm-linux.so (on Android) : > http://pastebin.com/X0Ngr8JP I see: 052c g F .text 0070 _vgnU_freeres which might be related to an intended replacement for __libc_freeres. > So effectively, there is no __libc_freeres in the symbol table. So, to

Re: [Valgrind-users] Getting segmentation fault @ ld-2.5.so for ARM

2011-05-04 Thread Wan Mohd Fairuz Wan Ismail
Hi /home/administrator/valgrind$ bin/valgrind -v -v -d -d > /root/valgrind_example > Can you try to move the program to more accessible directory such as /home/administrator and retry? > --1078-- Reading syms from /root/valgrind_example (0x8000) > --1078--svma 0x0082f8, avma 0x008

[Valgrind-users] Getting segmentation fault @ ld-2.5.so for ARM

2011-05-04 Thread Zaahir Khan
Hi All, I am new to valgrind. I am using valgrind 3.6.1 cross compiled for ARMv7. When I am memcheck getting SEGMENTATION FAULT @ /lib/ld-2.5.so. Is there any problem while configuration/Installation of valgrind? Log is below, any support highly appreciated. /home/administrator/valgrind$ bin/v

Re: [Valgrind-users] UME Error 22

2011-05-04 Thread Wan Mohd Fairuz Wan Ismail
Hi, I applied your patch and it seems to progress. The end value seems correct now. 0x1169c = (0xb0009000 - 0xb0001000) + 0x969c So, no more 2.9GB allocation which is good. Thanks to you. Then I re-test valgrind on Android and got this error : full output here -> http://pastebin.com/Gcz60MMM lin