From owner-freebsd-current  Sat May 16 02:40:17 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id CAA19312
          for freebsd-current-outgoing; Sat, 16 May 1998 02:40:17 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA19307;
          Sat, 16 May 1998 02:40:13 -0700 (PDT)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id TAA11548;
	Sat, 16 May 1998 19:40:10 +1000
Date: Sat, 16 May 1998 19:40:10 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199805160940.TAA11548@godzilla.zeta.org.au>
To: dyson@FreeBSD.ORG, peter@netplex.com.au
Subject: Re: libc corruption
Cc: current@FreeBSD.ORG, kkennawa@physics.adelaide.edu.au
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>To make it a little easier, perhaps have libc's syscall tables explicitly 
>generated from the kernel sources and committed.  That should make it 
>a no-brainer to keep them in sync and yet will stop accidental leakage 
>from the kernel into libc.

Better yet, generate the tables explicity and don't commit them anywhere.
That should make it a no-brainer to keep them in sync and stop accidental
blockage of the flow from the kernel into libc :-).

The flow was apparently blocked by not installing includes before
building libc.  syscall.mk is included from ${.CURDIR}/../../sys, but
syscall.h is included from <sys/>.

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message