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, 13 Jul 2000 12:13:03 -0400
To: cygwin <cygwin AT sources DOT redhat DOT com>
Subject: Re: runtime failure in 20000710 and 20000711 snapshots
Message-ID: <20000713121303.A9309@cygnus.com>
Mail-Followup-To: cygwin <cygwin AT sources DOT redhat DOT com>
References: <396D364D DOT 6A019EC1 AT ece DOT gatech DOT edu> <396DC0C4 DOT CA694EB7 AT cygnus DOT com> <396DE43E DOT FCC6B59F AT ece DOT gatech DOT edu> <396DE96B DOT FB70F492 AT ece DOT gatech DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <396DE96B.FB70F492@ece.gatech.edu>; from cwilson@ece.gatech.edu on Thu, Jul 13, 2000 at 12:08:11PM -0400

On Thu, Jul 13, 2000 at 12:08:11PM -0400, Charles Wilson wrote:
>The instruction at "0x00401a98" referenced memory at "0x00000001". The
>memory could not be "read".
>Click on OK to terminate the program
>Click on CANCEL to debug the program
>
>Is it expected that programs/dlls compiled with the new (20000711 and
>later) libcygwin.a will fail with older installations? 

If by "older installations" you mean "snapshots after 1.1.2", then yes.

I'm still tinkering with some of the startup code and I haven't resolved
things yet.  It is now very important to make sure that you are using a
libcygwin.a that goes with your cygwin1.dll.  Things are changing on
a daily basis.

I have made some changes to cygwin1.dll in the last few weeks that
can cause incompatibilities between "yesterday's snapshot" and "today's".
For a time, I also made changes that caused executables built with
"today's" libcygwin.a to be incompatible with cygwin1.dll v1.1.2.

Throughout all of this, however, I expect that executables built in the
last two years will still work correctly with any snapshot.  That's my
goal for 1.1.3, at least.  I also expect that when 1.1.3 is released,
executables linked with libcygwin.a will work correctly with 1.1.2.
They just will not be able to take advantage of some new functionality
in 1.1.3.

cgf

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