Messages in this thread | | | Date | Sun, 21 May 2006 11:35:12 -0700 | From | "Ulrich Drepper" <> | Subject | Re: IA32 syscall 311 not implemented on x86_64 |
| |
On 5/21/06, Dave Jones <davej@redhat.com> wrote: > It's a glibc problem really.
It's not a glibc problem really. The problem is this stupid error message in the kernel. We rely in many dozens of places on the kernel returning ENOSYS in case a syscall is not implemented and we deal with it appropriately. There is absolutely no justification to print these messages except perhaps in debug kernels. IMO the sys32_ni_syscall functions should just return ENOSYS unless you select a special debug kernel. One doesn't need the kernel to detect missing syscall implementations, strace can do this as well. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |