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 23:11:26 +0300
From: Egor Duda <deo AT logos-m DOT ru>
X-Mailer: The Bat! (v1.45) Personal
Reply-To: Egor Duda <cygwin-developers AT cygwin DOT com>
Organization: DEO
X-Priority: 3 (Normal)
Message-ID: <64255817646.20010311231126@logos-m.ru>
To: cygwin-developers AT cygwin DOT com
Subject: Re: Outstanding issues with current DLL?
In-reply-To: <20010311115725.A6747@redhat.com>
References: <20010307200848 DOT A32670 AT redhat DOT com> <s1slmqhyqvn DOT fsf AT jaist DOT ac DOT jp>
 <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>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

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()

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

CF> Maybe this will  also solve your "persistent dll" problem as well.
CF>    The   --enable-debugging   also  turns  on  lots  of  internal
CF> consistency checks in cygwin. 

i'm  far  from  thinking  that  all  those problems are due to several
cygwin1.dll, but here's my experience -- i run current cvs builds for
about   3  weeks  and it was rock stable on my system. so numerous bug
reports   was  quite  a  surprise   for  me.  but when i intentionally
left  2 different builds of cygwin1.dll on my system it really starts
to freeze and crash.

Egor.            mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19