Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com Date: Tue, 31 Aug 1999 20:40:04 -0400 From: Chris Faylor To: Mumit Khan Cc: cygwin-developers AT sourceware DOT cygnus DOT com Subject: Re: WARNING: previous dlopen of %s wasn't correctly performed Message-ID: <19990831204004.A2104@cygnus.com> Mail-Followup-To: Mumit Khan , cygwin-developers AT sourceware DOT cygnus DOT com References: <19990831011925 DOT A9493 AT cygnus DOT com> <199908311342 DOT IAA14819 AT mercury DOT xraylith DOT wisc DOT edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <199908311342.IAA14819@mercury.xraylith.wisc.edu>; from Mumit Khan on Tue, Aug 31, 1999 at 08:42:16AM -0500 On Tue, Aug 31, 1999 at 08:42:16AM -0500, Mumit Khan wrote: >Chris Faylor writes: >> Can anyone tell me what this error message signifies? I've got it coming fro >> m dlopen >> but I'm too tired to figure out why. > >If you're using dlopen, I may know have a clue; otherwise, sorry. > >Point your debugger to DllList::recordDll and check then "buf" and >_dlOpenedLib variables and that should provide a clue. > >The problem is quite possibly in DllList::recordDll, and usually has >to do with the fact the the DLL name given to dlopen doesn't match the >name Windows returns via GetModuleFileName later in recordDll. Usually >the problem is in case mismatch, and that should have been fixed by the >following patch: > >Sat May 22 19:03:47 1999 Mumit Khan > > * dll_init.cc (DllList::recordDll): Forkee must reload dlopened > DLLs. Also use strcasematch, not strcmp to compare file name. > >The other issue may very well have to do with symbolic links, however >it does appear to be taken care of in dlfcn.cc:get_full_path_of_dll. See >get_full_path_of_dll and check_access in dlfcn.cc for how a DLL name is >looked up. Thanks. This was what I needed. I was using the wrong entry point for a cygwin DLL. Duh. -chris