From owner-freebsd-toolchain@FreeBSD.ORG  Wed Feb  4 20:00:12 2015
Return-Path: <owner-freebsd-toolchain@FreeBSD.ORG>
Delivered-To: freebsd-toolchain@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 17050A6A
 for <freebsd-toolchain@freebsd.org>; Wed,  4 Feb 2015 20:00:12 +0000 (UTC)
Received: from mail-lb0-x22c.google.com (mail-lb0-x22c.google.com
 [IPv6:2a00:1450:4010:c04::22c])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 8C42AC9D
 for <freebsd-toolchain@freebsd.org>; Wed,  4 Feb 2015 20:00:11 +0000 (UTC)
Received: by mail-lb0-f172.google.com with SMTP id l4so3485588lbv.3
 for <freebsd-toolchain@freebsd.org>; Wed, 04 Feb 2015 12:00:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:sender:date:message-id:subject:from:to:content-type;
 bh=JakA2WUP6jE7Ob8OlUHB/laYXC+wAquYzfqms9wnFgI=;
 b=in9lqU4f8iXV0ZRyXM6+C+uYbK9o3c2ZbcRHlmM0GCJXMDD59UbDIO25JsUfBmNY0w
 xCWP61ZNqIE2vMIWH+O695fLxJL4ees3Uc3wjU2I9NG7n1CdMv5XYkG9gvXZEgLL121g
 d5tZur3VMhpXtvDUFzytMtbIgutWtNvx+9Yokwv+iDtJ8V3k6Ox2hICCL6YRUXiSi1d7
 XPqfEoovDDb8TcV/FibT9neuDb5LZn5UDmIZHH9uLkz2C7KZTDhyLA7VGJg9IBTWgOjR
 2g1SspFgd6uJmQmOev60r1A2AqY8LzAUGNC0dPMk6szX66wPbjKnR3JScYmkz+y+Mu26
 OKPA==
MIME-Version: 1.0
X-Received: by 10.112.181.231 with SMTP id dz7mr23474997lbc.47.1423080009592; 
 Wed, 04 Feb 2015 12:00:09 -0800 (PST)
Sender: crodr001@gmail.com
Received: by 10.112.28.40 with HTTP; Wed, 4 Feb 2015 12:00:09 -0800 (PST)
Date: Wed, 4 Feb 2015 12:00:09 -0800
X-Google-Sender-Auth: AfvE-Cwg36GZuwUCd_2uFdvL8Ko
Message-ID: <CAG=rPVfXbZ1YQHfKUSMXwBMsuNbgQWeNnWpaiJMROyaO2bhh=Q@mail.gmail.com>
Subject: Dependency walker for shared libraries in FreeBSD?
From: Craig Rodrigues <rodrigc@FreeBSD.org>
To: freebsd-toolchain@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1
X-BeenThere: freebsd-toolchain@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Maintenance of FreeBSD's integrated toolchain
 <freebsd-toolchain.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-toolchain>, 
 <mailto:freebsd-toolchain-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-toolchain/>
List-Post: <mailto:freebsd-toolchain@freebsd.org>
List-Help: <mailto:freebsd-toolchain-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-toolchain>, 
 <mailto:freebsd-toolchain-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Feb 2015 20:00:12 -0000

Hi,

On Windows, there is a tool, http://www.dependencywalker.com/ , that
can take a DLL as input, and then display all the dependencies that this
DLL has on other libraries.  This can be used to detect unresolved symbols.

Does anyone have a script that can do this on FreeBSD?
Basically, this would involve parsing the output of things like readelf,
nm, ldd, etc.

I tried looking for a similar tool on Linux, and found these:

https://launchpad.net/depspec
http://www.purinchu.net/software/elflibviewer.php
http://sourceforge.net/projects/binscan/

but I either couldn't build these tools, or the tools simply didn't work
under FreeBSD (elflibviewer).

--
Craig