and everything happens as usually, except
I have not achieved the goal of hitting any breakpoints.
Upon closer examination it appears that
the qemu-system-ppc64.exe that is linked to 0x400000 and up as any other
Windows application, in fact has been moved up higher in the address space
a number of pages, but not always the same number. I have seen 0xb600000
be the bias, and also 0x4c0000 and others. I found out by letting one of
my test output lines print the current EIP-value, as well as the (linked)
address of the function this happens inside. The 2 values were close to
each other as expected, and both were biased.
I must assume that the move of the qemu-system-ppc64.exe
sections means that this executable contains fixup relocations like what
the objdump tool reports:
file format pei-i386
Is there a way to have this work?
Is it important that relocation takes
place, or could it be fixed in the virtual address space as its usual 0x400000
I noticed the building of QEMU has -fPIC
at least for compilation of at least some files, but also --static.
Though I am only building this particular
qemu-system-ppc64 variant, it still takes me almost an hour to experiment
with other compile and link options.