Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 8 Nov 2002 18:23:49 -0800
From:      Steve Kargl <sgk@troutmask.apl.washington.edu>
To:        Brooks Davis <brooks@one-eyed-alien.net>
Cc:        "M. Warner Losh" <imp@bsdimp.com>, eischen@pcnet1.pcnet.com, ataraxia@cox.net, current@FreeBSD.ORG
Subject:   Re: [PATCH] note the __sF change in src/UPDATING
Message-ID:  <20021109022349.GA63634@troutmask.apl.washington.edu>
In-Reply-To: <20021108170523.B10496@Odin.AC.HMC.Edu>
References:  <20021108.142609.112624839.imp@bsdimp.com> <Pine.GSO.4.10.10211081806220.10745-100000@pcnet1.pcnet.com> <20021108.161606.79869853.imp@bsdimp.com> <20021108170523.B10496@Odin.AC.HMC.Edu>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Nov 08, 2002 at 05:05:23PM -0800, Brooks Davis wrote:
> On Fri, Nov 08, 2002 at 04:16:06PM -0700, M. Warner Losh wrote:
> > I'd love for there to be a way to know which binaries use __sF.
> 
> The following script run on your bin, sbin, lib, and libexec directories
> does a pretty decent job of finding files that contain refrences to __sF
> and listing the ports that use them (depend on portupgrade).
> 
> #!/bin/sh
> 
> sym=__sF
> 
> for file in $*; do
> 	if [ -n "`nm ${file} 2>&1 | egrep " ${sym}$"`" ]; then
> 		echo ${file} `pkg_which $file`
> 	fi
> done

nm doesn't work on shared libraries.  You can
use strings to find __sF in shared libs.

troutmask:kargl[201] cd /mnt/usr/lib/
troutmask:kargl[202] nm libm.a | grep sF
         U __sF
troutmask:kargl[203] nm libm.so.2 | grep sF
nm: libm.so.2: no symbols
troutmask:kargl[204] strings libm.so.2 | grep sF
__sF

-- 
Steve

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?20021109022349.GA63634>