* Fwd: Kernel stack trace for Winows 10 blue screen when running Cygwin? [not found] <CALXu0UfBK0+tYO_-3rgvZhpmKh8z4aVqMJMZ2=LfFmuJ1Vsmzw@mail.gmail.com> @ 2023-08-07 9:29 ` Cedric Blancher 2023-08-07 9:55 ` Corinna Vinschen 0 siblings, 1 reply; 4+ messages in thread From: Cedric Blancher @ 2023-08-07 9:29 UTC (permalink / raw) To: cygwin 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. 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 ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Kernel stack trace for Winows 10 blue screen when running Cygwin? 2023-08-07 9:29 ` Fwd: Kernel stack trace for Winows 10 blue screen when running Cygwin? Cedric Blancher @ 2023-08-07 9:55 ` Corinna Vinschen 2023-08-07 10:43 ` Cedric Blancher 0 siblings, 1 reply; 4+ messages in thread From: Corinna Vinschen @ 2023-08-07 9:55 UTC (permalink / raw) To: Cedric Blancher; +Cc: cygwin 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 ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Kernel stack trace for Winows 10 blue screen when running Cygwin? 2023-08-07 9:55 ` Corinna Vinschen @ 2023-08-07 10:43 ` Cedric Blancher 2023-08-07 11:23 ` Corinna Vinschen 0 siblings, 1 reply; 4+ messages in thread From: Cedric Blancher @ 2023-08-07 10:43 UTC (permalink / raw) To: cygwin On Mon, 7 Aug 2023 at 11:55, Corinna Vinschen <corinna-cygwin@cygwin.com> 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" 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! Ced ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Kernel stack trace for Winows 10 blue screen when running Cygwin? 2023-08-07 10:43 ` Cedric Blancher @ 2023-08-07 11:23 ` Corinna Vinschen 0 siblings, 0 replies; 4+ messages in thread From: Corinna Vinschen @ 2023-08-07 11:23 UTC (permalink / raw) To: Cedric Blancher; +Cc: cygwin On Aug 7 12:43, Cedric Blancher via Cygwin wrote: > On Mon, 7 Aug 2023 at 11:55, Corinna Vinschen <corinna-cygwin@cygwin.com> 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 ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2023-08-07 11:23 UTC | newest] Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- [not found] <CALXu0UfBK0+tYO_-3rgvZhpmKh8z4aVqMJMZ2=LfFmuJ1Vsmzw@mail.gmail.com> 2023-08-07 9:29 ` Fwd: Kernel stack trace for Winows 10 blue screen when running Cygwin? Cedric Blancher 2023-08-07 9:55 ` Corinna Vinschen 2023-08-07 10:43 ` Cedric Blancher 2023-08-07 11:23 ` Corinna Vinschen
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).