Re: Unknown cmd fd(5)
Hello Andreas,
On Thu, Mar 24, 2011 at 2:51 PM, Andreas Goesele <Goesele(a)hfph.mwn.de> wrote:
Hi.
When I start xemacs I get 20 times or so the following kernel messages:
Mar 24 15:56:32 computer kernel: [ 1565.560842] ioctl32(xemacs21-nomule:5715): Unknown
cmd fd(5) cmd(0000530a){t:'S';sz:0} arg(ffd6b35c) on socket:[46842]
I use a 64 bit kernel but a 32 bit system, don't know whether that's
related. Also don't know, whether these messages are related to my
crashes cf. <878vwnx7b7.fsf(a)debian.IGP> and <87oc5c5bm4.fsf(a)debian.IGP>
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