X-Spam-Check-By: sourceware.org
X-Envelope-From: <jonathan_lanier AT naughtydog DOT com>
X-Envelope-To: <cygwin AT cygwin DOT com>
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; 	charset="US-ASCII"
Subject: RE:  Re: 1.5.21-1: CIFS symlinks on network share break Cygwin
Date: Tue, 24 Oct 2006 14:25:19 -0700
Message-ID: <E173C70E3D81F74188D2778B96C5CD0D7FFD04@postal1-dog.naughtydog.com>
In-Reply-To: <ehlqvo$nh$3@sea.gmane.org>
From: "Jonathan Lanier" <jonathan_lanier AT naughtydog DOT com>
To: <cygwin AT cygwin DOT com>
X-Spam-Score: -11.44 () ALL_TRUSTED,USER_IN_WHITELIST
X-BorderEnvelope-To: <cygwin AT cygwin DOT com>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k9OLRQVu024998

Well, I thought of that - first rule of debugging, calculatus
eliminatus.  I tried it; but, attempts to use the older DLLs with newer
apps (or vice-versa) result in corrupted shared memory, and force me to
reboot my WinXP box.  I've been under the impression that cygwin1.dll
isn't really meant to be cross-compatible with applications built
against other versions of Cygwin, which would probably make the search
useless.  If anyone knows otherwise, I'm keen to hear anything about
cygwin1.dll-swapping that could be of use - i.e. how far back I could go
and expect to retain binary compatibility.

Of course, I could always reinstall the older versions complete from
scratch, but if I did that, I'd need to find archives of the older
Cygwins, and I'd probably use a different PC, as I spent a lot of time
configuring this one and I don't really want to blow Cygwin away if I
can help it.  I was kind of hoping someone here might have some idea
what was going on with the internals of Cygwin/WinXP that might provide
a more direct approach at solving the problem.  But if it comes to that,
then yes, I could try it.

- Jonathan Lanier


-----Original Message-----
From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com] On Behalf
Of Matthew Woehlke
Sent: Tuesday, October 24, 2006 12:53 PM
To: cygwin AT cygwin DOT com
Subject: Re: 1.5.21-1: CIFS symlinks on network share break Cygwin

Jonathan Lanier wrote:
> Also, because (I know the FAQ
> says not to say this, but I think it's useful information in this 
> case) we have a much older version of Cygwin (cygcheck reports 
> v1.5.14) that works flawlessly with CIFS and does not suffer the same 
> problems.  So, at the very least, it appears that something changed in

> Cygwin that is now exposing the undesired behavior.

This should be screaming "way to narrow down the problem" at you; IOW
you should try your test with various versions of cygwin1.dll, doing a
binary search, until you have a more specific idea of when the behavior
"broke".

--
Matthew
Only Joe suffers from schizophrenia. The rest of us enjoy it.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/