X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Mon, 10 Mar 2008 16:10:53 -0400
From:	David Arnstein <arnstein AT panix DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Problem with Cygwin and ClearCase
Message-ID:	<20080310201053.GA17124@panix.com>
Reply-To:	arnstein AT pobox DOT com
Mime-Version:	1.0
User-Agent:	Mutt/1.5.10i
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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

I just upgraded ClearCase to a new version and immediately I have
new problems relating to Cygwin. 

I use Windows XP Pro service pack 2, latest Cygwin, and ClearCase
7.0.1.0.

ClearCase tools such as clearexplorer.exe and clearvtree.exe run OK 
when launched from Windows. I can also launch them from a DOS box.

If I use a Cygwin bash script to launch a ClearCase tool then it gets
an application error. For example,
	Faulting application clearexplorer.exe, version 7.100.0.245,
	faulting module kernel32.dll, version 5.1.2600.3119, fault
	address 0x00012a5b.

Here's where it gets weird. 

I have ClearCase tools in the context menu of Windows Explorer. If I 
launch Windows Explorer from Windows, then I can launch these 
ClearCase tools from the context menu, no problem. However, if I 
	1. Launch Windows Explorer from a Cygwin bash script.
	2. Launch a ClearCase tool from the context menu of Windows
	   Explorer
then I get the application error again. I notice that when I launch
Windows Explorer in this way, I get a new Windows Explorer process. 

Similarly, if I 
	1. Launch a DOS box from Cygwin/bash by typing "cygstart cmd"
	2. Launch a ClearCase tool from the resulting DOS box
then I get the application error again.

I am writing to this mail list to inquire what is "special" about
processes started by a Cygwin bash process. "Special," when compared to
launching from a DOS box or from a standard Windows shortcut. Thanks
for any suggestions.

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

- Raw text -