X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 87C5E3858410
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1691402139;
	bh=Hr8iB94WlwI4Qql4e8HS/UqqYZ0CFUqCXKkRfN00QTg=;
	h=Date:To:Subject:References:In-Reply-To:List-Id:List-Unsubscribe:
	 List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc:
	 From;
	b=C4RoCq7hcorS9c5+ZWyblhiAt5LAva/geyljIY7D74xWyl9mQUi0BxB3qhQ06wTj2
	 kYZqvCw1zCPo4rY2HGg3UDcdZxLbUclE8R9IyM8BSEzDWdJ9D6hQP6OIl1d6whpiIn
	 pCdbdxy0sgb785q73VpGBRUmXQ+HL9OdArqzFMJI=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 602353858C39
Date: Mon, 7 Aug 2023 11:55:24 +0200
To: Cedric Blancher <cedric DOT blancher AT gmail DOT com>
Subject: Re: Kernel stack trace for Winows 10 blue screen when running Cygwin?
Message-ID: <ZNC/jK1A7iolJku4@calimero.vinschen.de>
Mail-Followup-To: Cedric Blancher <cedric DOT blancher AT gmail DOT com>,
 cygwin AT cygwin DOT com
References: <CALXu0UfBK0+tYO_-3rgvZhpmKh8z4aVqMJMZ2=LfFmuJ1Vsmzw AT mail DOT gmail DOT com>
 <CALXu0UewB26V01xbNTyTRPxCwtW_iyTD-_92_9WzrJLtwX6FwA AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <CALXu0UewB26V01xbNTyTRPxCwtW_iyTD-_92_9WzrJLtwX6FwA@mail.gmail.com>
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <https://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From: Corinna Vinschen via Cygwin <cygwin AT cygwin DOT com>
Reply-To: cygwin AT cygwin DOT com
Cc: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>, cygwin AT cygwin DOT com
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

On Aug  7 11:29, Cedric Blancher via Cygwin wrote:
> Forwarding to cygwin AT cygwin DOT com
> 
> Honestly I find it deeply concerning that a plain, unprivileged user
> can Bluescreen a machine, and more so that it happens during normal
> Cygwin usage.

Same here.  Cygwin is userspace only!

If any call in Cygwin can generate a bluescreen, it's a bug in the
kernel or in the driver.  Naturally, we have neither control over the
kernel, nor over the NTFS driver.  You might want to open a support case
with Microsoft.


Corinna


> 
> Ced
> 
> ---------- Forwarded message ---------
> From: Cedric Blancher <cedric DOT blancher AT gmail DOT com>
> Date: Sun, 6 Aug 2023 at 23:56
> Subject: Kernel stack trace for Winows 10 blue screen when running Cygwin?
> To: <cygwin-developers AT cygwin DOT com>
> 
> 
> Good evening!
> 
> How can we get a Windows kernel stack trace for a blue screen - aka
> Windows kernel crash?
> 
> We're experiencing regular blue screens when we run Cygwin git
> operations for a large repository (~6GB of text files, sort of DNA
> data).
> Usually it goes booom in the ntfs module with a git clone, or git
> commit, but a more detailed stack trace would be greatly appreciated.
> 
> Ced
> --
> Cedric Blancher <cedric DOT blancher AT gmail DOT com>
> [https://plus.google.com/u/0/+CedricBlancher/]
> Institute Pasteur
> 
> 
> -- 
> Cedric Blancher <cedric DOT blancher AT gmail DOT com>
> [https://plus.google.com/u/0/+CedricBlancher/]
> Institute Pasteur
> 
> -- 
> Problem reports:      https://cygwin.com/problems.html
> FAQ:                  https://cygwin.com/faq/
> Documentation:        https://cygwin.com/docs.html
> Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple