Hmmm, here's mine from mono-jit 2.0.1-4 (Jaunty). It does look like there has been a change to the way mono makes syscalls: the svc 0x9f0002 calls have gone, and svc 0 has appeared: this looks like a transition from the old syscall ABI to the new one.
Thanks.
Hmmm, here's mine from mono-jit 2.0.1-4 (Jaunty). It does look like there has been a change to the way mono makes syscalls: the svc 0x9f0002 calls have gone, and svc 0 has appeared: this looks like a transition from the old syscall ABI to the new one.
This still doesn't explain the problems I still got after enabling CONFIG_OABI_COMPAT. (See https:/ /bugs.launchpad .net/ubuntu/ +source/ mono/+bug/ 390591/ comments/ 13)
This may be explained by / related to the other bugs listed in this thread.
https:/ /bugs.launchpad .net/bugs/ 390802 /bugs.edge. launchpad. net/ubuntu/ +source/ f-spot/ +bug/390701
https:/
However, those are private so I have not been able to check.