I have another question vaguely related to my previous one. To recall,
I'm running QEMU in single-process mode on an ARM program, passing -d
exec,in_asm and trying to reconstruct the program's execution trace.
Unfortunately, I don't have as much information here, and the program
under test is
On 01/09/2015 06:03 PM, Peter Maydell wrote:
You're likely seeing the results of QEMU's TB chaining optimization.
Basically, if a jump target (or conditional jump target) is to a
known TB that we have already translated, we will patch it so that
we jump directly from one TB to the next without
On 9 January 2015 at 21:23, Evan Driscoll edrisc...@grammatech.com wrote:
I am running an ARM program in single-process mode with '-d exec', and
either the resulting traces are incomplete, I don't understand them, or
something else is going on. Tried with QEMU 2.2.0; more detailed info about
I am running an ARM program in single-process mode with '-d exec', and
either the resulting traces are incomplete, I don't understand them, or
something else is going on. Tried with QEMU 2.2.0; more detailed info
about how things are built run.
The suspicious part of the trace is:
