Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs Date: Thu, 5 Feb 2004 13:50:40 -0500 (EST) From: Igor Pechtchanski Reply-To: cygwin@cygwin.com To: cygwin@cygwin.com cc: peda@sectra.se Subject: Re: Segfault in _cygwin_dll_entry In-Reply-To: <6.0.1.1.0.20040205132314.02825cf8@127.0.0.1> Message-ID: References: <6.0.1.1.0.20040205132314.02825cf8@127.0.0.1> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: MIMEDefang 2.39 On Thu, 5 Feb 2004, Larry Hall wrote: > At 06:10 AM 2/5/2004, peda@sectra.se you wrote: > >Hello! > > > >I have been trying to get LibGGI to build and work on cygwin and > >I have the following problem: > > > >When I run an application linked against the resulting cygggi-2.dll > >it segfaults in _cygwin_dll_entry@12 (according to gdb) before main > >is reached. > > > >LibGGI consists of three core libraries: ggi, gii and gg. > > > >Now, cygggi-2.dll is linked against both cyggii-0.dll and > >cyggg-0.dll. cyggii-0.dll is in turn linked against cyggg-0.dll. I > >don't know if there is any relevance to this dependency tree, but > >I include it since programs linked directly against cyggii-0.dll > >does _not_ segfault. > > > >I can not find any relevant difference between how cygggi-2.dll and > >cyggii-0.dll are built. None of them defines a _cygwin_dll_entry, > >which means that cygwin should provide one, if I understand things > >correctly? > > > >strace on the failing application produces no output. > >The only other dlls these dlls depend on (directly) are cygwin1.dll > >and kernel32.dll (according to depends.exe provided with MSVC) > > > >How can I get more info on what is going on? > > I'd suggest 'cygcheck cygggi-2.dll'. Make sure there's no MS CRT in > there anywhere. If there is, you're on dangerous ground. Comparing the > output of this with that of cygii-0.dll might be instructive too. > > >Is it a known problem? > > No. If nothing "obvious" turns up in your initial efforts to scope the > problem, you're probably going to be best off debugging into the Cygwin > DLL to see where it crashes. One obvious thing to check for is whether the application tries to dynamically load a Cygwin-dependent DLL (which may result in attempting to load cygwin1.dll dynamically, and that is *not supported*). Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha@cs.nyu.edu ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "I have since come to realize that being between your mentor and his route to the bathroom is a major career booster." -- Patrick Naughton -- 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/