X-Spam-Check-By: sourceware.org Message-ID: <20060805225627.32929.qmail@web30612.mail.mud.yahoo.com> Date: Sat, 5 Aug 2006 18:56:27 -0400 (EDT) From: Martin Subject: Re: 1.5.21-1 DLL Loading Problem To: cygwin AT cygwin DOT com In-Reply-To: <44C6B776.2080600@zedasoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes 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 --- Rob Hatcherson wrote: > All: > > After installing 1.5.21-1 (cygcheck output attached) I've starting > experiencing a DLL loading problem whose presentation is similar to > that > of a problem described by Gary Zablackis in a 12-Apr-2006 post with > subject "Patch for silent crash with Cygwin1.dll v 1.5.19-4". > Examination of dll_init.cc shows that some variation of the suggested > > patch is part of 1.5.21-1. > > > The general situation is that I have a program that depends on > "B.dll", > which in turn depends on "A.dll". Both DLLs provide C++ classes. > The > symptom is that an attempt to launch the program comes back to the > shell > prompt without doing anything, i.e. no error messages, no output, no > anything else. If I statically link the program then it always > works. > > > Attempts to run in gdb in the dynamically linked case result in > output > similar to this: > > Starting program: /cygdrive/c/WorkAreas/... > > Program received signal SIGSEGV, Segmentation fault. > Error: dll starting at 0x4d1000 not found. > > Program received signal SIGSEGV, Segmentation fault. > > Program received signal SIGSEGV, Segmentation fault. > > Program exited with code 030000000005. > You can't do that without a process to debug. > > > The line "dll starting at 0x4d1000 not found" seemed to suggest that > I > have a path issue, but by inspection I don't believe this is the > case, > plus if I move the DLLs in question out of the way I get a different > response from gdb. > > > Google'ing hasn't yielded much yet. The post I referenced above is > the > closest thing I've found so far to the symptom I'm seeing. > > I've been trying to track this down with gdb, but haven't made much > progress. I put the cygwin1.dbg from the src distro into the /bin > dir, > which at least allowed some level of breakpoint setting, but so far > none > of the ones I've tried (dlopen, dll::init(), and a few others in that > > vicnity) have been hit. I'm not too familiar with the cygwin source > base, so I may be snooping around in the wrong spot. > > I've also been working on reducing the scenario down to some very > simple > libraries that reproduce the symptom reliably, but this hasn't > yielded > anything worth reporting yet. > > > In the meantime, does anyone have any suggestions regarding what's > going > on, and/or some other technique to catch this problem? > > Rob > === message truncated ===> -- I had a similar problem with dynamically loaded modules (extensions) in TCL. I traced my problem to the upgrade of binutils 20050610-1 to binutils 20060709-1. When I rolled it back, everthing was fine. However, I'm still running 1.5.20-1. Hope this helps, Martin __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- 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/