X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Fri, 9 Jan 2009 12:05:45 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: New "ldd" binary in snapshot and eventually in release Message-ID: <20090109170544.GA17048@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Note-from-DJ: This may be spam Last night, after seeing a request on irc, I did something that I've been meaning to do for many years - I wrote an "ldd" for Cygwin. The tricky part about writing ldd is getting it to display the load addresses of dlls that a program uses. I accomplished that by running the program up to its entry point, displaying the list of loaded dlls and their load addresses, and then terminating the process. I haven't verified this but ldd should work on any windows program. ldd itself is a cygwin program but the programs it inspects don't have to be. The output is similar to but not identical linux. The paths that it displays are in /cygwin/format. Btw, the techniques that I used may only work on Windows XP and above. I haven't confirmed that either. I haven't updated the documentation to include ldd yet but I expect to do that over the weekend. FYI. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/