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

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

> > So apart from some early architecture-specific parts of coregrind,
> > theoretically it ought to be straightforward to run an ARM-targeted
> > valgrind compiled as x86 then?
> 
> Theoretically, a complete instruction-by-instruction emulator for a user
mode
> process on Linux or QNX is a "straightforward" programming exercise.  In
> practice, that exercise takes a while.  The documentation is
> missing/incomplete/incorrect, for both the software and the hardware.  In
many
> cases an experiment or two [or more] is necessary to determine enough
truth to
> proceed.
> 
> Yes, it takes only 3 months to do "90%" of the job.  Then it takes 6 more
months
> to do the remaining _90%_, and a year after that until customers are
happy.

Sure. By straightforward I meant that one knows that if one keeps at the
problem, you'll eventually get there because the problem is trivial even if
lengthy i.e. implementation tends towards bounded time and resources. By
non-straightforward I would mean that no one knows the answer, or even if
there is an answer at all. Implementation there tends to be a cash hole.

Thanks for the advice. It's much appreciated.

Niall