|
From: Tom H. <to...@co...> - 2013-04-18 15:08:44
|
On 18/04/13 15:40, Niall Douglas wrote: > Perhaps I miscommunicated. QNX runs on x86 just as it does on ARM. It's > micro-kernel, so it can distribute. QNX prefers if the nodes it distributes > itself over are the same endian, but other than that it doesn't really care. > In other words, just to be absolutely clear, you can have an x86 QNX process > running on a PC yet using an ARM QNX kernel running on an attached ARM > device. That x86 QNX process will see a world identical in every way to as > if it were running on the ARM device: same filesystem, context switches, > everything. > > 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? Ah I misunderstood and thought you were talking about sending system calls from linux/x86 to QNX/arm. The problem with what you propose is that you've just moved your problem from needing to support system call translation (hard) to needing to support the QNX platform (also hard). Tom -- Tom Hughes (to...@co...) http://compton.nu/ |