On 2018-02-27 03:37 PM, Vince Rice wrote: >> On Feb 27, 2018, at 2:29 PM, Kaz Kylheku <920-082-4...@kylheku.com> wrote: >> >> On 2018-02-27 09:10, Numien wrote: >>> Jürgen Wagner nailed it; it was my antivirus, and disabling the >>> shellcode injection check fixed it. >> However, this time-wasting pattern of dealing with the issue by end users >> is not a good way. >> >> A better approach would be to identify some common paterns of BLODA >> interference >> and code a test which can detect the interference. This should be executed at >> startup by the Cygwin shell so that a diagnostic can be displayed to the >> user. >> >> WARNING: Cygwin detected interference from a "dodgy" application >> such as anti-virus software. Your Cygwin installation may malfunction. >> See http://<URL-to-BLODA-INFO> > We await your patch, but you might want to search the archives first. > https://cygwin.com/acronyms/#SHTDI
I would suggest at least putting a prominent link to the BLODA list near the top of https://cygwin.com/problems.html instead of 3rd from the bottom in the FAQ. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
