From owner-freebsd-current Mon Jun 17 17:55:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA13219 for current-outgoing; Mon, 17 Jun 1996 17:55:25 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA13211 for ; Mon, 17 Jun 1996 17:55:23 -0700 (PDT) Received: from jraynard.demon.co.uk (ao111.du.pipex.com [193.130.254.111]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id RAA28147 for ; Mon, 17 Jun 1996 17:55:09 -0700 Received: (from fcurrent@localhost) by jraynard.demon.co.uk (8.7.5/8.6.12) id OAA10606; Mon, 17 Jun 1996 14:37:54 GMT Date: Mon, 17 Jun 1996 14:37:54 GMT Message-Id: <199606171437.OAA10606@jraynard.demon.co.uk> From: James Raynard To: bde@zeta.org.au CC: bde@zeta.org.au, freebsd-current@freebsd.org, j@uriah.heep.sax.de, nate@sri.MT.net In-reply-to: <199606170202.MAA11393@godzilla.zeta.org.au> (message from Bruce Evans on Mon, 17 Jun 1996 12:02:21 +1000) Subject: Re: ktrace [Was: 2.2-960612-SNAP resolver problems] Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >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