Hey Martin,
the next problem that I'm facing now is that I don't know how to access
the instruction that caused the pagefault. I have the instruction
pointer but not the instruction itself (opcode and operands).
Your vinit code [1] uses an imprint to identify the corresponding
Rm_client and
Hi Martin,
No, continue_after_resolved_fault DOES continue execution (although the
IP isn't yet the one you need), what I meant is that you can't do this
in vanilla Genode from userland (not core) without attaching an
appropriate dataspace. So, you have already extended the RM session by
an RPC
Hello,
I circumvented the problem of finding the correct dataspace by letting
the pagefault handler open another ROM connection to the binary at its
instantiation. The ELF file contains the VM address of the code section,
which allows me to fetch the correct instruction when a pagefault
happens.
