|
From: Александар М. <dar...@gm...> - 2011-11-11 16:50:39
|
Thanks for the input, but the thing is - i'm running on a proprietary board (running on ARMv7+VFP); for which android has been specifically ported. I'm avoiding to disclose potentially sensitive (confidential) info, but here's the deal: When I first try to configure with the arm-eabi compiler I got with this SDK, valgrind doesn't recognize the OS and returns... then i configure it with arm-linux-gnueabi, i've added support for all ARM processors (config.sh, line 5288 or so, changed armv7* to arm*) and that goes well. After I get the compiled binary, I put it in the rootfs folder used for booting up the board, like any other file. That's why I know it's not a PATH issue, because it's the exact same procedure i do for every other app and they *always* get found without absolute pathing. >From what I understood, the "official" way states that it only works on Nexus S, but I know for sure it can run on our board as well - some collegues (which i can't get hold of currently) have used it without too much hassle. But here's what it is: android sdk is on my VM. the rootfs is on the board. there is no /external/valgrind/coregrind/valgrind on the board, it's just /system/bin/valgrind. Every other app I put there becomes "visible" instantly as i work with a live NFS. I really don't know why valgrind is acting up and pretending not to be there when it clearly IS there. I can't even get it to scan through LS, so a hello_world.c won't do me much good either I suppose... but I can try. So, how do I help you help me without breaching any NDAs? :) P.S. I have to compile Valgrind with -static (err... link it statically) for it to run on the board when using the said arm-linux-gnueabi compiler. |