Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: Sun, 11 Mar 2001 15:43:13 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Subject: Re: Outstanding issues with current DLL?
Message-ID: <20010311154313.A22735@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com
References: <20010307213711 DOT E32721 AT redhat DOT com> <3AA79E39 DOT BC915295 AT yahoo DOT com> <20010308125701 DOT A4371 AT redhat DOT com> <3AA7CCBA DOT E84FD16E AT yahoo DOT com> <20010308133552 DOT A878 AT redhat DOT com> <3AA7E05A DOT BF9F2535 AT yahoo DOT com> <20010310184508 DOT A16745 AT redhat DOT com> <002701c0aa26$d372d010$0200a8c0 AT voyager> <20010311115725 DOT A6747 AT redhat DOT com> <64255817646 DOT 20010311231126 AT logos-m DOT ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.11i
In-Reply-To: <64255817646.20010311231126@logos-m.ru>; from deo@logos-m.ru on Sun, Mar 11, 2001 at 11:11:26PM +0300

On Sun, Mar 11, 2001 at 11:11:26PM +0300, Egor Duda wrote:
>Hi!
>
>Sunday, 11 March, 2001 Christopher Faylor cgf AT redhat DOT com wrote:
>
>CF> Btw, the reason for the --enable-debugging switch is to build a cygwin1.dll
>CF> which timestamps all of its shared memory stuff.  This allows two versions
>CF> of cygwin to be running on the system at the same time.
>
>do   we   really   need   this?  suppose a some problem  reports about
>current  snapshots  we've  seen  here this week can be due  to several
>cygwin1.dll's.  at least freezes can be easily explained if we suppose
>such  possibility. when process 'exec's some cygwin program which sees
>other  cygwin1.dll,  it surely will break in an unpredictable way when
>doing fdtab.fixup_after_exec in dll_crt0_1()

Hopefully the version numbering in the exec header should catch this.
I'll bump it up, just to make sure.

>using  CYGWIN_TESTING  environment  variable was enough for me, and at
>least i always knew what i doing.

CYGWIN_TESTING is a relatively new addition by DJ which just adapted
code that had been in Cygwin for two or three years.

So, yes, we need this.  I've been using it for a long time and I
rely on it.

I didn't say that this was foolproof.  It is far from it.  If it was
foolproof it would be the default.  However, I find it invaluable for
testing.

If this is really the cause of people's problem reports, I'll be surprised.
I just fixed one of these and it certainly wasn't due to disparate cygwin
DLL versions.

cgf