From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 2155) id D025D388215B; Mon, 7 Aug 2023 11:23:44 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D025D388215B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1691407424; bh=fNwi/VWdv9zziT1W3fS6dry3VWC1A2AhvpfcZ850u1s=; h=Date:From:To:Cc:Subject:Reply-To:References:In-Reply-To:From; b=bSsOdGDDemENxrS1U1cgZTe/aLe08J6dHL2Ap5AwSgO7iNs8oMY5NX/F8/+qetJ0c 56qgpnSj8SElZ9Nz+PgSmb/ZeclUw0YkpeWl1XLlcDqoRRLBUTF6umIm1iOnpJMXuS 1V+lSfRLqr9It4T3drDaYmwBWjPQ+sGDqzy24jWU= Received: by calimero.vinschen.de (Postfix, from userid 500) id 0E299A80BDA; Mon, 7 Aug 2023 13:23:43 +0200 (CEST) Date: Mon, 7 Aug 2023 13:23:43 +0200 From: Corinna Vinschen To: Cedric Blancher Cc: cygwin@cygwin.com Subject: Re: Kernel stack trace for Winows 10 blue screen when running Cygwin? Message-ID: Reply-To: cygwin@cygwin.com Mail-Followup-To: Cedric Blancher , cygwin@cygwin.com References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: List-Id: On Aug 7 12:43, Cedric Blancher via Cygwin wrote: > On Mon, 7 Aug 2023 at 11:55, Corinna Vinschen wrote: > > > > 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. > > 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