Date: Tue, 18 Aug 1998 23:13:31 +0200 (CEST) From: wjw@digi.digiware.nl (Willem Jan Withagen) To: tlambert@primenet.com (Terry Lambert) Cc: hackers@FreeBSD.ORG Subject: Re: Getting a new syscall to work Message-ID: <199808182113.VAA17496@digi.digiware.nl> In-Reply-To: <199808170559.WAA20804@usr09.primenet.com> from Terry Lambert at "Aug 17, 98 05:59:32 am"
next in thread | previous in thread | raw e-mail | index | archive | help
=> > I've followed most all of the receipe which was given by Eric A. Davis => > to add a systemcall. But now I'm all out of idea's: => > => > /usr/libexec/ld.so: Undefined symbol "___nsysctl" called from testnsysctl:/usr/lib/libc.so.3.2 at 0x200857d8 => > (I bumped the minor number.) => > => > I've looked in the running kernel with nm: => > f0124c4c T ___nsysctl => > f01241a0 F nsysctl.o => > => > So as far I know, things should be working. => > But they don't, so can somebody give me a new pointer => => You must put it in the libc as well as in the kernel. => => If you know the number, a good developement stopgap would be to call => syscall(2) with the number as the first argument, the calls first => argument as the second argument, etc.. Very good suggestion. I should have thought of it myself. Proves that I have the call in the kernel, and that the pilot-error is libc. thanx, --WjW To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199808182113.VAA17496>