|
From: John R. <jr...@bi...> - 2013-04-18 15:06:24
|
> So what I'm saying is: discount any worries about paths and libraries not > matching up. What remains in valgrind itself to get an x86 compiled binary > to valgrind an ARM executable? Early parts of coregrind run some tests on the host (x86 in this case) to figure out what kind of environment coregrind is operating in. The handling of signals (sigaction(), signal handlers, etc.) is delicate: various things must match between host and target. -- |