From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: Cedric Blancher <cedric.blancher@gmail.com>
Cc: cygwin-developers@cygwin.com
Subject: Re: Kernel stack trace for Winows 10 blue screen when running Cygwin?
Date: Mon, 7 Aug 2023 10:35:29 +0200 [thread overview]
Message-ID: <ZNCs0VWTJ6npcfjo@calimero.vinschen.de> (raw)
In-Reply-To: <CALXu0UfBK0+tYO_-3rgvZhpmKh8z4aVqMJMZ2=LfFmuJ1Vsmzw@mail.gmail.com>
Wrong mailing list, use cygwin AT cygwin DOT com for user questions.
On Aug 6 23:56, Cedric Blancher wrote:
> 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
prev parent reply other threads:[~2023-08-07 8:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-06 21:56 Cedric Blancher
2023-08-07 8:35 ` Corinna Vinschen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZNCs0VWTJ6npcfjo@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cedric.blancher@gmail.com \
--cc=cygwin-developers@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).