From: David Macek <david.macek.0@gmail.com>
To: cygwin-patches@cygwin.com
Subject: [PATCH] Add Forefront TMG to the BLODA
Date: Tue, 24 Nov 2015 22:29:00 -0000 [thread overview]
Message-ID: <5654E4CE.4020105@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1379 bytes --]
A user of MSYS2 had non-deterministic segfaults when running simple command from bash started from cmd. We've isolated the cause to `C:\Program Files (x86)\Forefront TMG Client\FwcWsp64.dll`. See <http://sourceforge.net/p/msys2/tickets/212/> for a little more information.
It seems enough to include the software in BLODA, but if not, sorry for the unsolicited patch and let's discuss.
* faq-using.xml: Add Forefront TMG to the BLODA
---
winsup/doc/faq-using.xml | 1 +
1 file changed, 1 insertion(+)
diff --git a/winsup/doc/faq-using.xml b/winsup/doc/faq-using.xml
index 4cfc822..35370f6 100644
--- a/winsup/doc/faq-using.xml
+++ b/winsup/doc/faq-using.xml
@@ -1317,6 +1317,7 @@ behaviour which affect the operation of other programs, such as Cygwin.
<listitem><para>AVAST (disable FILESYSTEM and BEHAVIOR realtime shields)</para></listitem>
<listitem><para>Citrix Metaframe Presentation Server/XenApp (see <ulink url="http://support.citrix.com/article/CTX107825">Citrix Support page</ulink>)</para></listitem>
<listitem><para>Lavasoft Web Companion</para></listitem>
+<listitem><para>Forefront TMG</para></listitem>
</itemizedlist></para>
<para>Sometimes these problems can be worked around, by temporarily or partially
disabling the offending software. For instance, it may be possible to disable
--
2.6.2.windows.1
--
David Macek
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4254 bytes --]
reply other threads:[~2015-11-24 22:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5654E4CE.4020105@gmail.com \
--to=david.macek.0@gmail.com \
--cc=cygwin-patches@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).