Re: STATUS_ACCESS_VIOLATION/segfault problems with cygwin 1.1.4

[Chris Faylor <cgf at cygnus dot com>]

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@delorie.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@sourceware.cygnus.com