Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
From:	Chris Faylor <cgf AT cygnus DOT com>
Date:	Thu, 14 Sep 2000 18:49:47 -0400
To:	cygwin AT sourceware DOT cygnus DOT com
Subject:	Re: STATUS_ACCESS_VIOLATION/segfault problems with cygwin 1.1.4
Message-ID:	<20000914184947.A25215@cygnus.com>
Reply-To:	cygwin AT sources DOT redhat DOT com
Mail-Followup-To:	cygwin AT sourceware DOT cygnus DOT com
References:	<20000914135833 DOT D19083 AT cygnus DOT com> <200009141930 DOT PAA06711 AT envy DOT delorie DOT com> <39C1648D19D DOT 375BKG AT icarus DOT une DOT edu DOT au>
Mime-Version:	1.0
User-Agent:	Mutt/1.3.6i
In-Reply-To:	<39C1648D19D.375BKG@icarus.une.edu.au>; from kg@kgb.une.edu.au on Fri, Sep 15, 2000 at 09:51:41AM +1000

On Fri, Sep 15, 2000 at 09:51:41AM +1000, Klint Gore wrote:
>On Thu, 14 Sep 2000 15:30:52 -0400, DJ Delorie <dj AT delorie DOT com> wrote:
>> The problem is when you have two differently named import libraries
>> that refer to the same DLL.  Because they have different names, the
>> linker sorts them separately, but because they are the same
>> internally, there is only one symbol for the import, and half the
>> imports get ignored.
>
>I'm not sure if it's the same problem, but I get this
>STATUS_ACCESS_VIOLATION when trying to compile squid. GCC reports the
>following
>
>      0 [main] cc1 1065 handle_exceptions: Exception: STATUS_ACCESS_VIOLATION
>    623 [main] cc1 1065 stackdump: Dumping stack trace to cc1.exe.stackdump
>gcc: Internal compiler error: program cc1 got fatal signal 11
>make: *** [uudecode.o] Error 1
>
>Anyone want to have a go at what that means?  It happens after a lot of
>parse errors and warnings in winsock.h.

It's not the same problem.  That one would be a gcc bug.

If you fix the parse errors you'll probably stop the SIGSEGV.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -