Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <027c01c1beaa$58a32850$0200a8c0@lifelesswks> From: "Robert Collins" To: "Lagstein, Yossi" , References: Subject: Re: 1.3.4 - touch /etc/abc causes BSOD Date: Tue, 26 Feb 2002 20:45:37 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-OriginalArrivalTime: 26 Feb 2002 09:44:36.0689 (UTC) FILETIME=[33DC7C10:01C1BEAA] === ----- Original Message ----- From: "Lagstein, Yossi" To: ; Sent: Tuesday, February 26, 2002 5:56 PM Subject: RE: 1.3.4 - touch /etc/abc causes BSOD > It may be Microsoft bug, but since The trigger for the BSOD is cygwin, and > I'm unable to reproduce it with non cygwin relegated software, I hope that > other people that encounter the same or similar problem may have some idea > on how to solve the it I understand your hope, but it is fallacious. The correct way to debug this is _already_ documented by MS, at the locations you showed. The first step is to identify the failing component: NTKERNEL.EXE, and the second step to contact the manufacturer: MS. Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/