Kernel stack trace for Winows 10 blue screen when running Cygwin?

Mon Aug 7 09:55:24 GMT 2023

On Aug 7 11:29, Cedric Blancher via Cygwin wrote:
> Forwarding to cygwin@cygwin.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.blancher@gmail.com>
> Date: Sun, 6 Aug 2023 at 23:56
> Subject: Kernel stack trace for Winows 10 blue screen when running Cygwin?
> To: <cygwin-developers@cygwin.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.blancher@gmail.com>
> [https://plus.google.com/u/0/+CedricBlancher/]
> Institute Pasteur
>>> -- 
> Cedric Blancher <cedric.blancher@gmail.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