Hello Andreas, On Thu, Mar 24, 2011 at 2:51 PM, Andreas Goesele <Goesele(a)hfph.mwn.de&gt; wrote: That means that something invoked ioctl(5, 0x530a, 0xffd6b35c), and the kernel is complaining that it doesn't know anything about a 0x530a ioctl command for that socket (see compact_ioctl_error() in fs/compat_ioctl.c in the Linux kernel sources). This probably indicates that your XEmacs was built with out of date kernel headers. If so, rebuilding XEmacs will fix the problem. If rebuilding doesn't help or isn't feasible, then we can try to figure this out with the debugger. Put a breakpoint on ioctl and start XEmacs. If you have the glibc debug sources installed and gcc hasn't optimized the args away, you may be able to set a conditional breakpoint (something like "break ioctl if request == 0x530a"). Otherwise, you'll just have to continue each time some other ioctl call is made. Once you get to the bad ioctl call, get a backtrace and send us another message. Regards, -- Jerry James http://www.jamezone.org/ _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta