Kernel stack trace for Winows 10 blue screen when running Cygwin?
Mon Aug 7 10:43:01 GMT 2023
On Mon, 7 Aug 2023 at 11:55, Corinna Vinschen <email@example.com> wrote:
> On Aug 7 11:29, Cedric Blancher via Cygwin wrote:
> > Forwarding to firstname.lastname@example.org
> > 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.
Well, a colleague is handling that. The feedback sent to her however was that:
- Cygwin is not a Windows product
- We should WSL instead
- Cygwin might make use private Windows apis
- We should run this by the "Cygwin company"
It is my turn now to provide a kernel stack trace to prove them wrong
- IF I can manage to make one. That's why I am asking for help here.
More information about the Cygwin