Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Reply-To: Cygwin List <cygwin AT cygwin DOT com>
Message-Id: <6.0.1.1.0.20040205132314.02825cf8@127.0.0.1>
X-Sender: 
Date: Thu, 05 Feb 2004 13:30:40 -0500
To: peda AT sectra DOT se, cygwin AT cygwin DOT com
From: Larry Hall <cygwin-lh AT cygwin DOT com>
Subject: Re: Segfault in _cygwin_dll_entry
In-Reply-To: <OFA12C58A5.82CA2073-ONC1256E31.00388442@dbs.sectra.se>
References: <OFA12C58A5 DOT 82CA2073-ONC1256E31 DOT 00388442 AT dbs DOT sectra DOT se>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 06:10 AM 2/5/2004, peda AT sectra DOT 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 AT 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.



--
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746                     


--
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/