Date: Sat, 16 May 1998 20:36:34 +0800 From: Peter Wemm <peter@netplex.com.au> To: Bruce Evans <bde@zeta.org.au> Cc: current@FreeBSD.ORG, dyson@FreeBSD.ORG, kkennawa@physics.adelaide.edu.au Subject: Re: libc corruption Message-ID: <199805161236.UAA02664@spinner.netplex.com.au> In-Reply-To: Your message of "Sat, 16 May 1998 22:12:55 %2B1000." <199805161212.WAA18632@godzilla.zeta.org.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Bruce Evans wrote:
> >> >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 :-).
> >
> >This is the present situation and it's not working very well.
>
> It isn't the present situation. We commit the tables to src/sys and
> use some tables from <sys>, some from src/sys/sys, and even some from
> src/sys/kern (see src/usr.bin/kdump/kdump.c). We only generate the
> tables on the fly for truss (see src/usr.bin/truss/Makefile).
I'm talking about libc.. The syscall stub list is generated on the fly
and the binary interface is affected.
Cheers,
-Peter
--
Peter Wemm <peter@netplex.com.au> Netplex Consulting
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199805161236.UAA02664>