This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
Re: bluescreen during XF86/cygwin build
- To: "Dave Cook" <dcook at caveduck dot com>,<cygwin-xfree at cygwin dot com>,<cygwin at cygwin dot com>
- Subject: Re: bluescreen during XF86/cygwin build
- From: "Robert Collins" <robert dot collins at itdomain dot com dot au>
- Date: Sun, 27 May 2001 14:05:23 +1000
- References: <002501c0e662$0ed24a60$6800a8c0@dbca950>
----- Original Message -----
From: "Dave Cook" <dcook@caveduck.com>
To: <cygwin-xfree@cygwin.com>; <cygwin@cygwin.com>
Sent: Sunday, May 27, 2001 2:03 PM
Subject: Fw: bluescreen during XF86/cygwin build
> I suspect this may be a cygwin DLL problem but it has only ever
manifested for me while
> building XFree86/Cygwin, so I'm posting to both lists.
It shouldn't be either. Cygwin doesn't install any drivers at this point
in time. I suspect your system.
> A command of the following form at bash prompt on a freshly pulled
XFree86 CVS tree caused
> identical "driver has corrupted the executive memory pool"
bluescreens 3 times in a row:
Have you looked into what driver and the call stack for the bluescreen?
Rob
> make World | tee world.log
>
> I think a couple of the attempts used 2>&1 stderr redirection. System
is Win2000 SP2,
> Cygwin 1.3.1, not using ntsec. Plenty of disk and ram available. The
crash happens
> during the massive rm's done in the cleaning stage at the start of the
build. If I change
> the command to
>
> make World > world.log
>
> everything is fine.
>
> Regards,
>
> Dave Cook
>
>