X-Spam-Check-By: sourceware.org
Message-ID: <453EBCFD.7070308@cygwin.com>
Date: Tue, 24 Oct 2006 21:25:17 -0400
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh AT cygwin DOT com>
Reply-To: cygwin AT cygwin DOT com
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.7) Gecko/20060916 Fedora/1.5.0.7-1.fc4.remi Thunderbird/1.5.0.7 Mnenhy/0.7.4.0
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: 1.5.21-1: CIFS symlinks on network share break Cygwin
References: <E173C70E3D81F74188D2778B96C5CD0D7FFD04 AT postal1-dog DOT naughtydog DOT com> <453E980D DOT 3070104 AT cygwin DOT com> <BAY109-DAV463AF7DBA1647EA548DACEB060 AT phx DOT gbl>
In-Reply-To: <BAY109-DAV463AF7DBA1647EA548DACEB060@phx.gbl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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

<http://cygwin.com/acronyms/#TOFU>.  Reformatted.

Champ Mendis wrote:
> ----- Original Message ----- From: "Larry Hall (Cygwin)" 
> <reply-to-list-only-lh <AT> cygwin <DOT> com>
> To: <cygwin <AT> cygwin <DOT> com>
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

<http://cygwin.com/acronyms/#PCYMTNQREAIYR>.  Thanks.

> Sent: Wednesday, October 25, 2006 8:47 AM
> Subject: Re: 1.5.21-1: CIFS symlinks on network share break Cygwin
> 
> 
>> Jonathan Lanier wrote:
>>> 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.
>>>
>>
>> There is backwards binary compatibility but not forward.  So I'd suggest,
>> if you're interested in trying this, that you use your 1.5.14 environment
>> and swap in DLLs until it doesn't work.  But keep your original DLL so 
>> you
>> can "reset" it at the end.  Start with the oldest snapshot and binary 
>> search
>> your way in.
> Hi,
> I got the same problem, I ran Insight debugger too but it failed. Code 
> very well in new version of Cygwin but
> Exe file does not give any output. Insight debugger says unknown error.
> I was wondering whether XP Media Edition is conflicting with Cygwin 
> environment.
> I tried the Cygwin1.dll to run in DOS mode but it failed.
> I will also try the same thing as Jonathan says.


Two additional thoughts on this:

  o If you have a small, simple test case in C, it's worth your while
    to consider sending it to the list.

  o You should send along your cygcheck output.  Indeed, it's worthwhile to
    re-read <http://cygwin.com/problems.html>.  The more relevant details,
    the better! :-)


-- 
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
216 Dalton Rd.                          (508) 893-9889 - FAX
Holliston, MA 01746

--
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/