public inbox for
 help / color / mirror / Atom feed
From: Adam Dinwoodie <>
Subject: Re: Does the Cygwin setup program do internal sanity checks on startup?
Date: Thu, 25 Aug 2022 17:52:42 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Wed, Aug 24, 2022 at 08:46:10PM +0000, Brian Cowan via Cygwin wrote:
> Why would I ask that question? Because I have a host running a
> hodgepodge of company-mandated security software, and -- only on that
> host -- the Cygwin setup tool crashes...
> Oddities:
> 1. The crash generates 3 dump files when I use procdump, which is odd
> since I "normally" only get 2 identical dumps from procdump.
> 2. A Websense ForcePoint DLP DLL is loaded in the process space,
> apparently through DLL injection.
> 3. There seem to be 3 threads started, only one of which is the setup
> program's "main" function. I had to get that out of a Process Monitor
> log since the dump files are largely content free.
> 4. The crash is unique to the setup program. Nothing else appears to
> fail.
> The crash is an "illegal instruction" dump, which of course doesn't
> make a lot of sense... This could be one of the other security
> packages/policies on this host being "helpful."
> I need ammunition to take to my internal Mordak's so I can update
> Cygwin... Sure I can use WSL, but not for everything.

This sounds like classic "BLODA": applications that interfere with how
Cygwin provides *nix compatibility.  There's more info in the FAQs at, but in short it seems
very likely that this problem is caused by some security software
running on this system.

  reply	other threads:[~2022-08-25 16:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-24 20:46 Brian Cowan
2022-08-25 16:52 ` Adam Dinwoodie [this message]
2022-08-25 17:11   ` Jon Turney
2022-08-25 18:14     ` Brian Cowan
2022-08-28 15:46       ` Jon Turney
2022-08-31 12:14         ` Brian Cowan
2022-09-03 13:02           ` Andrey Repin

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).