> I am worried about PTRACE_SYSEMU, I continue to ignore this magic
> which I don't understand yet... Hopefully I will be able to add the
> necessary changes later.

It should not be a big complexity.  The semantics is that the entry report
always does like UTRACE_SYSCALL_ABORT to skip the actual call, and then
there is no exit report.  (Since ptrace doesn't distinguish entry and exit
reports, you can make the actual stop and report happen either in the entry
spot or the exit spot, whatever is easiest in the implementation.)


Thanks,
Roland

Reply via email to