> Also check which syscall code is passed to syscall trap (in
> arch/powerpc/trap.c:179).

I beleive I didn't understand very well what you suggested here. Why
would Netscape or any Linux binary call sys_syscall, which does not
exist on Linux?

I added some printf where you told me. NetBSD binaries do a lot of
syscall calls (code 173, 197 and 199, but a Linux binary never calls
sys_syscall.

> IIRC Linux on i386 doesn't have special syscall(2) syscall and has
> something else as syscall number 0. It is probably similar on
> powerpc. Maybe it causes some problems ?

syscall number zero returns ENOSYS on Linux. What problems could this
cause? 

-- 
Emmanuel Dreyfus
UNIX *is* user friendly. It is just a bit selective about his friends
p99dreyf@criens.u-psud.fr