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
In-Reply-To: <Pine.GSO.4.61.0507111118450.7597@slinky.cs.nyu.edu>
To: cygwin AT cygwin DOT com
Subject: Re: Inconsistent behavior for Win32 executable: starting from 	bashvs. starting   from cmd.exe
MIME-Version: 1.0
Message-ID: <OF87156D7D.7B679C09-ONC125703B.0057DAA2-C125703B.0059E3F2@philips.com>
From: Ljubomir Milanovic <ljubomir DOT milanovic AT philips DOT com>
Date: Mon, 11 Jul 2005 18:19:33 +0200
Content-Type: text/plain; charset="US-ASCII"

Hi,

Thanks for hints from Igor Pechtchanski and Dave Korn. The problem
was indeed PATH variable on cygwin side. I made a typo and defined
PATH under cmd.exe only as cygwin\bin directory and same invalid
address error was result (surprise, surprise :). After few trial/error
cycles the fix was to add ClearCase bin directory to the PATH under
cygwin !!! Don't ask me why.

However, program is now working properly also if started from bash.

Thank you very much for help,
Bye,
Ljubo

P.S.
My PATH under windows is huge, and I redefined windows PATH in
cygwin to avoid too long "search" times, e.g. if pressing TAB at empty
line and similar. However, as my problem shows, this praxis has some 
risks.

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