Date: Mon, 17 Jun 1996 14:37:54 GMT From: James Raynard <fcurrent@jraynard.demon.co.uk> To: bde@zeta.org.au Cc: bde@zeta.org.au, freebsd-current@freebsd.org, j@uriah.heep.sax.de, nate@sri.MT.net Subject: Re: ktrace [Was: 2.2-960612-SNAP resolver problems] Message-ID: <199606171437.OAA10606@jraynard.demon.co.uk> In-Reply-To: <199606170202.MAA11393@godzilla.zeta.org.au> (message from Bruce Evans on Mon, 17 Jun 1996 12:02:21 %2B1000)
next in thread | previous in thread | raw e-mail | index | archive | help
> >The error message is not particularly informative, either:- > >ktrace -f foobar ls > >ktrace: "): Function not implemented. This has obviously been through something that's not 8-bit clean. The actual error message was ktrace: U?iU?i"U?i)U?i: Function not implemented. where 'U' was a capital U with a grave accent, '?' was an inverted question mark and 'i' was a lower case i with an umlaut! In fact, this is caused by error() being invoked without any arguments. NetBSD's ktrace implementation does this much more cleanly, using err() and warn(). Any objections if I make the necessary modifications? > Why doesn't it get a SIGSYS? Answer: someone "fixed" the ktrace syscall to > always exist and return ENOSYS if KTRACE is not configured. This breaks the > usual handling of unimplemented syscalls, which is to generate SIGSYS and > return EINVAL. Thanks, I was wondering about that. Presumably this can be "un-fixed" in the obvious way (ie shuffling some #ifdef/#endif's around)? > Grepping for ENOSYS in /sys/kern shows the same bug in oquota() and ENOSYS > being confused with ENOTTY in pipe_ioctl(). Ditto? Cheers -- James Raynard, Edinburgh, Scotland james@jraynard.demon.co.uk
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199606171437.OAA10606>