|
From: Lu M. <kin...@gm...> - 2013-10-21 21:23:32
|
Hello all, none-x86-linux could be used as a binary translator, which generate i386 binary with input of i386 executable. On the other hand, none-amd64-linux could be used for amd64-amd64 translation. I am wondering whether it is possible to use valgrind for i386-x86_64 translation, which means the input is i386 executable and generate x86_64 binary in code cache. Thanks a lot. |
|
From: Philippe W. <phi...@sk...> - 2013-10-21 21:31:51
|
On Tue, 2013-10-22 at 05:23 +0800, Lu Mitnick wrote: > Hello all, > > > none-x86-linux could be used as a binary translator, which generate > i386 binary with input of i386 executable. On the other hand, > none-amd64-linux could be used for amd64-amd64 translation. I am > wondering whether it is possible to use valgrind for i386-x86_64 > translation, which means the input is i386 executable and generate > x86_64 binary in code cache. In theory yes. In practice, I think it will imply a significant effort to get this working. Philippe |
|
From: Lu M. <kin...@gm...> - 2013-10-21 21:59:17
|
Hello Philippe, Thanks your reply. Is it means that the option of host and target should be the same when we configured? Thanks a lot |
|
From: Philippe W. <phi...@sk...> - 2013-10-22 17:37:27
|
On Tue, 2013-10-22 at 05:59 +0800, Lu Mitnick wrote: > Hello Philippe, > > > Thanks your reply. Is it means that the option of host and target > should be the same when we configured? Yes, currently configuring valgrind to run on one arch, but execute a program from another arch is not supported. Philippe |