Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!apple!voder!pyramid!ctnews!risky!pase70!scottl
From: scottl@convergent.com (Scott Lurndal)
Newsgroups: comp.unix.wizards
Subject: Re: Shared libraries: what functions are dynamically linked in?
Message-ID: <4254@risky.Convergent.COM>
Date: 25 Apr 91 18:35:09 GMT
References: <47793@ut-emx.uucp>
Sender: root@risky.Convergent.COM
Reply-To: scottl@convergent.com (Scott Lurndal)
Distribution: usa
Organization: Unisys Network Computing Group
Lines: 20

In article <47793@ut-emx.uucp>, pefv700@perv.pe.utexas.edu writes:
|> In article <7355@auspex.auspex.com>, guy@auspex.auspex.com (Guy Harris) writes...

|> Say you have a.out, a stripped executable that was linked dynamically with
|> a shared library.  (nm won't work here, right?)  Assuming I did it right,
|> ldd only told me, "Yes, it's using this shared library."  But I want to
|> know the functions in the shared library that will be used when the
|> executable is exec'd.

For non-stripped executables:

    nm a.out | grep UNDEF

for stripped executables:

    dump -v -s -n .dynsym a.out  | grep UNDEF

(This works on SVR4.0 systems)

scott