X-Spam-Check-By: sourceware.org Date: Thu, 24 Aug 2006 12:32:32 -0400 (EDT) From: Igor Peshansky Reply-To: cygwin AT cygwin DOT com To: Pierre Baillargeon cc: cygwin AT cygwin DOT com Subject: Re: no message or dialog when a DLL is missing In-Reply-To: <44EDA26C.6000603@innobec.com> Message-ID: References: <44ECC152 DOT 3020503 AT innobec DOT com> <44EDA26C DOT 6000603 AT innobec DOT com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 On Thu, 24 Aug 2006, Pierre Baillargeon wrote: > Igor Peshansky wrote: > > > You really haven't given us enough to go on here. What is the > > program, which DLL is it missing, how do you know it requires it, etc, > > etc. > > I know, because it's a program I wrote. It's a DLL loaded by the Windows > loader. It's *not* from LoadLibrary() nor dlopen(). What compiler was used to build the program? What does "cygcheck YOURPROGRAM" say? Is this a Cygwin program or a pure Windows one? If a pure Windows one built with, say, MSVC, see if you can get the same problem when using "gcc -mno-cygwin"... > I also know because when launched in cmd.exe, I get the usual Windows > dialog about missing DLL. It's the same dialog when you double-click on > the executable in Windows Explorer. The name of the DLL would not tell > you much, since one of our own DLL. > > I was mostly curious why the difference in behavior and how to get the > "standard" behavior instead of silent failure. We'd have to look and see. Please try to reduce it down to a minimal reproducible testcase (i.e., one that simply tries to load a DLL, with the DLL itself being an empty library), and post it along with build instructions. We'll then see if there is something in Cygwin that prevents the pop-up. > I suspected that the way cygwin launches program was by first supressing > system dialogs. ( I don't remember the trick off hand, but I remember > reading about it about how to supress error dialogs when accessing > CD-ROM drives that may not contain media.) It's certainly possible to do this in Windows, but I doubt Cygwin goes into that much effort to avoid popping up the missing DLL dialogs. Once we see your testcase, we can think of further steps to track it down. I'm not ruling out a bug in Cygwin, but we need to be able to reproduce the symptoms before we can pass judgement. HTH, Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu | igor AT watson DOT ibm DOT com ZZZzz /,`.-'`' -. ;-;;,_ Igor Peshansky, Ph.D. (name changed!) |,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte." "But no -- you are no fool; you call yourself a fool, there's proof enough in that!" -- Rostand, "Cyrano de Bergerac" -- 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/