X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2E68938D7FDF
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1691408854;
	bh=WqTz4Cy1Dk1cFQWWzxvVUG0Z9nM5Bgi91skDZHyc+O4=;
	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=T+/Qa26+ipIFR6GJhbN/Hymw6WRXDdSQ8sumfjDtYPS7WQdFT/A+hLIyiQ6PM51gs
	 +azZ6J39gN/oOrJCLY4wsdOhoecCPLbAi/9lQeBcWhhbeK2nUMC47wqniY86SqtSF6
	 /EwLEnde5BXjGiYlsp1pMvuETaZzZcLINOI08tR0=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D025D388215B
Date: Mon, 7 Aug 2023 13:23:43 +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: <ZNDUPyf5I0YKxCtl@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>
 <ZNC/jK1A7iolJku4 AT calimero DOT vinschen DOT de>
 <CALXu0UfsYo=CMpApdVWF5S3Vw5pwMbB70o0UJ9tdHDE05gHGOw AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <CALXu0UfsYo=CMpApdVWF5S3Vw5pwMbB70o0UJ9tdHDE05gHGOw@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 12:43, Cedric Blancher via Cygwin wrote:
> On Mon, 7 Aug 2023 at 11:55, Corinna Vinschen <corinna-cygwin AT cygwin DOT com> wrote:
> >
> > 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.
> 
> 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"

ROFL

> 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.
> 
> HELP!

I'd start with running the crashing process under strace.  This might
give a clue as to what or why it's happening.  Be aware that an strace
might be *very* big in your case, and that running under strace might
take a *very* long time.

Apart from that, I'm not really familiar with catching OS kernel dumps,
but the dumper and minidumper tools in Cygwin might be of help, see the
docs:

https://cygwin.com/cygwin-ug-net/dumper.html
https://cygwin.com/cygwin-ug-net/minidumper.html


Corinna

-- 
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