Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin/>
List-Help:	<mailto:cygwin-help AT sourceware DOT cygnus DOT com>,
	<http://sourceware.cygnus.com/ml/#faqs>
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Message-Id:	<199907262314.SAA03424@mercury.xraylith.wisc.edu>
To:	Craig Wyllie <craig AT halcyon DOT ca>
cc:	cygwin AT sourceware DOT cygnus DOT com
Subject:	Re: PurifyNT 6.0.1 with complex Cygnus Cygwin build environment and NT Performance Registry data access
In-Reply-To:	Your message of "Mon, 26 Jul 1999 16:21:28 EDT."
	<Pine DOT GSO DOT 4 DOT 05 DOT 9907261619310 DOT 4491-100000 AT columbia>
Date:	Mon, 26 Jul 1999 18:14:13 -0500
From:	Mumit Khan <khan AT xraylith DOT wisc DOT EDU>

Craig Wyllie <craig AT halcyon DOT ca> writes:
> 
> We are currently using Cygnus' Gnupro Toolkit to build an NT port of a
> Sun Solaris application, which will access the NT performance registry.
> 
> We are unable to complete Purification of the resultant executables,
> the purified application exits without any warning or error messages
> after an extended period at 100% cpu.

Since Rational claims that it only works with Visual C++ 5.0 and 6.0,
I'm not surprised that it doesn't work with Cygwin. Purify is a very
intrusive tool (OCI and all that), and needs quite a bit of knowledge 
of runtime libs, and especially the memory manager used which for
Cygwin is dramatically different from MSVC's.

Perhaps speak with your customer rep at Rational?

Regards,
Mumit


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -