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
Date: Tue, 6 Sep 2005 14:01:52 +1000 (EST)
From: Luke Kendall <luke DOT kendall AT cisra DOT canon DOT com DOT au>
Subject: Re: Odd transient error about __impure_ptr
To: cygwin AT cygwin DOT com
In-Reply-To: <Pine.GSO.4.63.0509052347120.504@slinky.cs.nyu.edu>
MIME-Version: 1.0
Content-Type: TEXT/plain; CHARSET=US-ASCII
Message-Id: <20050906040152.62A9083C6F@pessard.research.canon.com.au>

On  5 Sep, Igor Pechtchanski wrote:
>  Hard to say without a proper problem report[*], but it sounds like you 
>  have another version of cygwin1.dll in the PATH.  Windows looks for 
>  cygwin1.dll in the directory of the program before it looks at the PATH, 
>  and the standard cygwin.bat runs bash from /bin, so it finds the new DLL. 
>  If your shell.exe is in another directory, the older DLL in the PATH will 
>  take precedence. 

That's along the lines of what I thought.  What puzzled me was how it
just went away without even me having to logg out, let alone reboot. I
think I'll just put it down as one of those weird Windows things.

Thanks,

luke


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