From owner-freebsd-stable  Fri Mar  9  1:18:15 2001
Delivered-To: freebsd-stable@freebsd.org
Received: from daedalus.cs.brandeis.edu (daedalus.cs.brandeis.edu [129.64.3.179])
	by hub.freebsd.org (Postfix) with ESMTP id 1519D37B718
	for <stable@freebsd.org>; Fri,  9 Mar 2001 01:18:13 -0800 (PST)
	(envelope-from meshko@daedalus.cs.brandeis.edu)
Received: from localhost (meshko@localhost)
	by daedalus.cs.brandeis.edu (8.9.3/8.9.3) with ESMTP id EAA23842;
	Fri, 9 Mar 2001 04:18:10 -0500
Date: Fri, 9 Mar 2001 04:18:10 -0500 (EST)
From: Mikhail Kruk <meshko@cs.brandeis.edu>
To: Andrew Hesford <ajh3@chmod.ath.cx>
Cc: <stable@freebsd.org>
Subject: Re: top/systat
In-Reply-To: <20010309025639.B19665@cec.wustl.edu>
Message-ID: <Pine.LNX.4.30.0103090407540.23474-100000@daedalus.cs.brandeis.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

[skip]

> When you try to run top, it looks for the symbol that represents nlist,
> and when it can't find it, it doesn't know where to find the nlist
> kernel function. I'm guessing nlist has something to do with a process
> list... hence, when top can't find nlist, it throws a fit.

I think nlist *is* the list of symbols. What I get from reading
kvm_nlist() it tries to lookup a given list of symbols in kernel. If it
fails, top gives up.
KVM_NLIST(3) more or less explains it.

Now I have another questions: it seems that under some conditions
kvm_nlist can fall back to some other method of getting the values:

	/*
	 * If we can't use the kld symbol lookup, revert to the
	 * slow library call.
	 */
	if (!ISALIVE(kd))
		return (__fdnlist(kd->nlfd, nl));

so my question is: whould this fdnlist work in abscence of kernel symbols?


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