Summary: | valgrind dies with failed in UME only for dynamically linked binaries, works fine for static binaries | ||
---|---|---|---|
Product: | [Developer tools] valgrind | Reporter: | Sundeep <gitta471> |
Component: | general | Assignee: | Julian Seward <jseward> |
Status: | RESOLVED NOT A BUG | ||
Severity: | normal | CC: | tom |
Priority: | NOR | ||
Version: | 3.6.0 | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
cpu_loop source code
log of cpu_loop dynamically linked program run thorugh valgrind strace log of cpu_loop dynamically linked program run through valgrind statically linked program run on valgrind works fine |
Description
Sundeep
2011-03-15 10:01:20 UTC
Created attachment 58019 [details]
log of cpu_loop dynamically linked program run thorugh valgrind
Created attachment 58020 [details]
strace log of cpu_loop dynamically linked program run through valgrind
Created attachment 58021 [details]
statically linked program run on valgrind works fine
Android isn't really a supported platform yet, so you're probably better off addressing this with the people that are working on porting valgrind to android than report it here as none of us have any experience of valgrind on android. (In reply to comment #4) > Android isn't really a supported platform yet, so you're probably better off > addressing this with the people that are working on porting valgrind to android > than report it here as none of us have any experience of valgrind on android. From the strace log and valgrind log data, I come to a stand that it is breaking in loading the exe file onto memory. Can you please give some more info on why this can happen, So, that I can try fixing it. As I said, valgrind is not currently supported on android and nobody here is going to be able to help you. There are people working on android port and I suggest you talk to them. There is bug tracking the progress they have made so far which you can see here: https://bugs.kde.org/show_bug.cgi?id=266035 The problem you are seeing is most likely caused by incompatibilities between the address space layout on android and how valgrind likes to arrange memory, such that something can't be loaded at the required address. It will need careful debugging by somebody with good knowledge of both valgrind and the kernel being used and access to an appropriate system on which to debug it. |