Re: [Valgrind-developers] Valgrinding an ARM process using an x86 built valgrind

[Niall D. <ndo...@bl...>]

> > I was wondering what would be the issues, if any, of valgrinding a
> > foreign architecture process e.g. building an x86 build of ARM
> > valgrind and then using that to valgrind an ARM executable on an x86
> > machine? Obviously it could load a local set of foreign architecture
> > shared libraries etc. easily enough. I can see perhaps though that the
> > syscall kernel interface might vary, and that could be a problem.
> >
> > Other than that though, what would stand in the way? Surely as it
> > emulates the instruction set it ought to work right?
> 
> This is not supported at all.
> 
> Yes, in theory VEX might be able to cross translate the code (though I
think there
> might be problems even there) but the big stumbling block is that there is
> absolutely no support for translating system calls from one architecture
to
> another.

Thanks for the answer.

Let us assume that system calls aren't a problem, as we can work around
those here thanks to QNX's micro kernel nature by simply pushing syscalls
over an IP link. What would be the next major show stopper, purely from
within valgrind itself?

Thanks,
Niall