Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Message-ID: <00ef01c0ecd6$41559c60$0200a8c0@lifelesswks> From: "Robert Collins" To: "Andy Moreton" , References: <006801c0ecd5$db486d80$2b0b070a AT cam DOT virata DOT com> Subject: Re: dlsym discussion.. Date: Mon, 4 Jun 2001 19:10:51 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-OriginalArrivalTime: 04 Jun 2001 09:02:03.0884 (UTC) FILETIME=[05FA1AC0:01C0ECD5] ----- Original Message ----- From: "Andy Moreton" > > > -----Original Message----- > > Looking at this from the Win32 side of things, perhaps you should look at > the ToolHelp library, in particular CreateToolHelp32Snapshot(), > Module32First(), > and Module32Next(). > > This will give you a list of all modules for the current process. Checking > the > module handle against the list maintained by cygwin should give the > information > you need. > > HTH, > > AndyM > Neato. That combined with before/after dlopen will also let me grab the dependant libraries that are automatically loaded as well. That won't be fool proof, but it's better than nothing. I suppose we could fall back to walking the entire list anyway, but that would likely return erroneous results :-[ You wouldn't happen to know of an equivalent function for NT 4.0 would you? (MSND lists that function as win95+, Windows 2000+. Rob