Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 31 Dec 1998 08:58:21 +1100 (EST)
From:      Darren Reed <darrenr@reed.wattle.id.au>
To:        phk@critter.freebsd.dk (Poul-Henning Kamp)
Cc:        mike@smith.net.au, committers@FreeBSD.ORG
Subject:   Re: kvm_nlist emulation of n_type from kld symbol table at runtime.
Message-ID:  <199812302158.IAA18737@avalon.reed.wattle.id.au>
In-Reply-To: <91478.915047292@critter.freebsd.dk> from "Poul-Henning Kamp" at Dec 30, 98 08:48:12 pm

next in thread | previous in thread | raw e-mail | index | archive | help
In some email I received from Poul-Henning Kamp, sie wrote:
>
> In message <199812301938.LAA04955@dingo.cdrom.com>, Mike Smith writes:
> >
> >> Nutshell: Can anybody forsee the need to export symbol type to userland?
> >>
> >No, the obvious solution is to improve and expand the sysctl interface,
> >which already provides size and type information.
>
> It would be trivial to implement in a sysctl, and we can even do it
> as
>       sysctl kern.nlist.val.avenrun
>       sysctl kern.nlist.type.avenrun
> if you want to...

I'd just like to point out that, if people haven't already noticed, that
relying on sysctl alone to provide this sort of interface does not help
anybody and creates more work for porting regular applications to FreeBSD.

Sure, provide a sysctl interface by all means, but if you are going to 
support exporting the internal symbol table to user programs then IMHO
doing so in a manner which is already widely supported is essential.

Then again, I won't be coding it, just expecting tools such as nm, gdb,
or anything else which uses the nlist() library function to just work
as if the sysctl interface was a regular file with a symbol table.


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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199812302158.IAA18737>