Outstanding issues with current DLL?

Egor Duda deo@logos-m.ru
Mon Mar 12 07:23:00 GMT 2001


Sunday, 11 March, 2001 Christopher Faylor cgf@redhat.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()

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

ah. i found the thing that confused me. it really suppose to timestamp
shared  region  name,  but  it seems to me that it doesn't. version.cc
checks if DEBUGGING is set, but it doesn't include config.h.
should we

Index: cygwin_version.h
RCS file: /cvs/src/src/winsup/cygwin/cygwin_version.h,v
retrieving revision 1.1
diff -u -p -1 -r1.1 cygwin_version.h
--- cygwin_version.h    2000/09/08 02:56:54     1.1
+++ cygwin_version.h    2001/03/12 15:09:06
@@ -10,2 +10,6 @@ details. */
+# include "config.h"
 #include <cygwin/version.h>


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

More information about the Cygwin-developers mailing list