Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-Id:	<4.3.1.2.20010116150345.0230e268@pop.ma.ultranet.com>
X-Sender:	lhall AT pop DOT ma DOT ultranet DOT com
X-Mailer:	QUALCOMM Windows Eudora Version 4.3.1
Date:	Tue, 16 Jan 2001 15:07:11 -0500
To:	Andrew Heath <ah228 AT cornell DOT edu>, cygwin AT cygwin DOT com
From:	"Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com>
Subject:	Re: DLL problems
In-Reply-To:	<4.3.2.7.2.20010116150118.02fc6508@postoffice2.mail.cornell
	.edu>
Mime-Version:	1.0

At 03:04 PM 1/16/2001, Andrew Heath wrote:
>I have an executable that I've compiled with the -mwindows and -mno-cygwin switches, and it runs just fine, except at start up time on Win9X boxes.  If I start the program in the users login script, I get a page fault in CRTDLL.DLL, but not on the WinNT boxen.  Any ideas as to cause?


Yes, its the penalty for using a bad O/S!;-)

Seriously, its difficult to even speculate as to the issue without seeing 
some information about your environment and the crash.  Output of cygcheck
-s -v -r may be helpful.  A stack trace is more likely to be helpful.  
However, its probably something you just have to debug yourself to narrow
down the possibilities...



Larry Hall                              lhall AT rfk DOT com
RFK Partners, Inc.                      http://www.rfk.com
118 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX



--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -