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
Date: Fri, 21 Jun 2002 13:01:55 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: cygwin1.dll [1.3.11(CVS)]: Changes since 06/19 snapshot cause page fault in kernel32.dll
Message-ID: <20020621170155.GA19453@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20020620114252 DOT 64865 DOT qmail AT web21003 DOT mail DOT yahoo DOT com> <8228727568 DOT 20020620172306 AT syntrex DOT com> <830819686 DOT 20020620175758 AT syntrex DOT com> <20020620171628 DOT GB5605 AT redhat DOT com> <751591979 DOT 20020620204954 AT gmx DOT net> <20020620191835 DOT GC5605 AT redhat DOT com> <965316664 DOT 20020620215159 AT gmx DOT net> <268469348 DOT 20020620224431 AT gmx DOT net> <10634038194 DOT 20020621184629 AT syntrex DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <10634038194.20020621184629@syntrex.com>
User-Agent: Mutt/1.3.23.1i

On Fri, Jun 21, 2002 at 06:46:29PM +0200, Pavel Tsekov wrote:
>PT>> 3) The new binutils has something to do with the crash
>
>I've found the following:
>
> Old 'ld'(200110) seems to place the following symbols and the first
> '.data_cygwin_nocopy' on a the same  place - '_data_end__' and
> 'wsock_started'.
>
> New 'ld' places them in the following order:
>   1. '_data_end__'
>   2. first '.data_cygwin_nocopy' section and 'wsock_started' starting
>      4 bytes after '_data_end__'.
>
>Of course it may have nothing to do with the crash - if so just tell me
>and I'll shut up :)

That's actually an interesting observation.  Thanks.

I can confirm that the test version of binutils is doing something
funky.  I've removed that version from sourceware.

What's really odd is that the version of binutils that I run under linux
to produce the snapshots (and the upcoming 1.3.11 release) seems to work
fine.

One problem with the bad DLL is that the constructor list is empty.  While
that speeds up startup enormously, it does cause the type of problems that
you're seeing.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/