Differences between 20071227 and 20071230

diff -p -N -d -r -U2 winsup-src-20071227/cygwin-snapshot-20071227-1/winsup/cygwin/cygwin.din winsup-src-20071230/cygwin-snapshot-20071230-1/winsup/cygwin/cygwin.din
--- winsup-src-20071227/cygwin-snapshot-20071227-1/winsup/cygwin/cygwin.din	2007-12-21 15:05:56.000000000 +0000
+++ winsup-src-20071230/cygwin-snapshot-20071230-1/winsup/cygwin/cygwin.din	2007-12-30 22:07:17.000000000 +0000
@@ -378,4 +378,7 @@ __f_ldexp = _f_ldexp NOSIGFE
 _f_ldexpf NOSIGFE
 __f_ldexpf = _f_ldexpf NOSIGFE
+_f_llrint NOSIGFE
+_f_llrintf NOSIGFE
+_f_llrintl NOSIGFE
 _f_log NOSIGFE
 __f_log = _f_log NOSIGFE
@@ -386,8 +389,14 @@ __f_log10f = _f_log10f NOSIGFE
 _f_logf NOSIGFE
 __f_logf = _f_logf NOSIGFE
+_f_lrint NOSIGFE
+_f_lrintf NOSIGFE
+_f_lrintl NOSIGFE
 _f_pow NOSIGFE
 __f_pow = _f_pow NOSIGFE
 _f_powf NOSIGFE
 __f_powf = _f_powf NOSIGFE
+_f_rint NOSIGFE
+_f_rintf NOSIGFE
+_f_rintl NOSIGFE
 _f_tan NOSIGFE
 __f_tan = _f_tan NOSIGFE
@@ -846,4 +855,7 @@ listen = cygwin_listen SIGFE
 llabs NOSIGFE
 lldiv NOSIGFE
+llrint = _f_llrint NOSIGFE
+llrintf = _f_llrintf NOSIGFE
+llrintl = _f_llrintl NOSIGFE
 localeconv NOSIGFE
 _localeconv = localeconv NOSIGFE
@@ -876,6 +888,7 @@ _longjmp = longjmp NOSIGFE
 lrand48 NOSIGFE
 _lrand48 = lrand48 NOSIGFE
-lrint NOSIGFE
-lrintf NOSIGFE
+lrint = _f_lrint NOSIGFE
+lrintf = _f_lrintf NOSIGFE
+lrintl = _f_lrintl NOSIGFE
 lround NOSIGFE
 lroundf NOSIGFE
@@ -1200,8 +1213,7 @@ rexec = cygwin_rexec SIGFE
 rindex NOSIGFE
 _rindex = rindex NOSIGFE
-rint NOSIGFE
-_rint = rint NOSIGFE
-rintf NOSIGFE
-_rintf = rintf NOSIGFE
+rint = _f_rint NOSIGFE
+rintf = _f_rintf NOSIGFE
+rintl = _f_rintl NOSIGFE
 rmdir SIGFE
 _rmdir = rmdir SIGFE
diff -p -N -d -r -U2 winsup-src-20071227/cygwin-snapshot-20071227-1/winsup/cygwin/include/cygwin/version.h winsup-src-20071230/cygwin-snapshot-20071230-1/winsup/cygwin/include/cygwin/version.h
--- winsup-src-20071227/cygwin-snapshot-20071227-1/winsup/cygwin/include/cygwin/version.h	2007-12-28 02:19:10.000000000 +0000
+++ winsup-src-20071230/cygwin-snapshot-20071230-1/winsup/cygwin/include/cygwin/version.h	2007-12-30 22:07:21.000000000 +0000
@@ -320,4 +320,7 @@ details. */
       177: Export sys_sigabbrev
       178: Export wcpcpy, wcpncpy.
+      179: Export _f_llrint, _f_llrintf, _f_llrintl, _f_lrint, _f_lrintf,
+	   _f_lrintl, _f_rint, _f_rintf, _f_rintl, llrint, llrintf, llrintl,
+	   rintl, lrintl, and redirect exports of lrint, lrintf, rint, rintf.
      */
 
@@ -325,5 +328,5 @@ details. */
 
 #define CYGWIN_VERSION_API_MAJOR 0
-#define CYGWIN_VERSION_API_MINOR 178
+#define CYGWIN_VERSION_API_MINOR 179
 
      /* There is also a compatibity version number associated with the
diff -p -N -d -r -U2 winsup-src-20071227/cygwin-snapshot-20071227-1/winsup/doc/faq-setup.xml winsup-src-20071230/cygwin-snapshot-20071230-1/winsup/doc/faq-setup.xml
--- winsup-src-20071227/cygwin-snapshot-20071227-1/winsup/doc/faq-setup.xml	2006-08-26 19:11:00.000000000 +0000
+++ winsup-src-20071230/cygwin-snapshot-20071230-1/winsup/doc/faq-setup.xml	2007-12-30 22:07:17.000000000 +0000
@@ -156,4 +156,8 @@ disk if you are paranoid.
 something malicious, and no mirror has been compromised.
 </para>
+<para>See also <ulink url="http://cygwin.com/faq/faq.using.html#faq.using.bloda" />
+for a list of applications that have been known, at one time or another, to
+interfere with the normal functioning of Cygwin.
+</para>
 </answer></qandaentry>
 
diff -p -N -d -r -U2 winsup-src-20071227/cygwin-snapshot-20071227-1/winsup/doc/faq-using.xml winsup-src-20071230/cygwin-snapshot-20071230-1/winsup/doc/faq-using.xml
--- winsup-src-20071227/cygwin-snapshot-20071227-1/winsup/doc/faq-using.xml	2007-07-18 15:43:37.000000000 +0000
+++ winsup-src-20071230/cygwin-snapshot-20071230-1/winsup/doc/faq-using.xml	2007-12-30 22:07:17.000000000 +0000
@@ -634,4 +634,8 @@ Note that with many of these products, s
 does not remove these changes; it must be completely uninstalled.
 </para>
+<para>See also <ulink url="http://cygwin.com/faq/faq.using.html#faq.using.bloda" />
+for a list of applications that have been known, at one time or another, to 
+interfere with the normal functioning of Cygwin.
+</para>
 </answer></qandaentry>
 
@@ -783,4 +787,8 @@ would be <literal>C:\cygwin\bin</literal
 exploited by a hostile non-Cygwin program, so do this at your own risk.
 </para>
+<para>See also <ulink url="http://cygwin.com/faq/faq.using.html#faq.using.bloda" />
+for a list of applications that have been known, at one time or another, to
+interfere with the normal functioning of Cygwin.
+</para>
 </answer></qandaentry>
 
@@ -951,2 +959,85 @@ elsewhere in this FAQ.
 </para></answer></qandaentry>
 
+<qandaentry id="faq.using.bloda">
+<question><para>What applications have been found to interfere with Cygwin?</para></question>
+<answer>
+
+<para>From time to time, people have reported strange failures and problems in
+Cygwin and Cygwin packages that seem to have no rational explanation.  Among
+the most common symptoms they report are fork failures, memory leaks, and file
+access denied problems.  These problems, when they have been traced, often appear
+to be caused by interference from other software installed on the same PC.  Security
+software, in particular, such as anti-virus, anti-spyware, and firewall applications,
+often implements its functions by installing hooks into various parts of the system,
+including both the Explorer shell and the underlying kernel.  Sometimes these hooks
+are not implemented in an entirely transparent fashion, and cause changes in the
+behaviour which affect the operation of other programs, such as Cygwin.
+</para>
+<para>Among the software that has been found to cause difficulties are:</para>
+<para><itemizedlist>
+<listitem><para>Sonic Solutions burning software containing DLA component</para></listitem>
+<listitem><para>Norton/MacAffee/Symantec antivirus or antispyware</para></listitem>
+<listitem><para>Logitech webcam software with "Logitech process monitor" service</para></listitem>
+<listitem><para>Kerio, Agnitum or ZoneAlarm Personal Firewall</para></listitem>
+<listitem><para>Iolo System Mechanic/AntiVirus/Firewall</para></listitem>
+<listitem><para>LanDesk</para></listitem>
+<listitem><para>Windows Defender </para></listitem>
+<listitem><para>Embassy Trust Suite fingerprint reader software wxvault.dll</para></listitem>
+<listitem><para>NOD32 Antivirus</para></listitem>
+<listitem><para>ByteMobile laptop optimization client</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
+on-access scanning in your antivirus, or configure it to ignore files under the
+Cygwin installation root.  Often, unfortunately, this is not possible; even disabling
+the software may not work, since many applications that hook the operating system
+leave their hooks installed when disabled, and simply set them into what is intended
+to be a completely transparent pass-through mode.  Sometimes this pass-through is not
+as transparent as all that, and the hooks still interfere with Cygwin; in these cases,
+it may be necessary to uninstall the software altogether to restore normal operation.
+</para>
+<para>Some of the symptoms you may experience are:</para>
+<para><itemizedlist>
+<listitem>
+<para>Random fork() failures.</para>
+<para>Caused by hook DLLs that load themselves into every process in the
+system.  POSIX fork() semantics require that the memory map of the child process
+must be an exact duplicate of the parent process' layout.  If one of these DLLs
+loads itself at a different base address in the child's memory space as compared
+to the address it was loaded at in the parent, it can end up taking the space that
+belonged to a different DLL in the parent.  When Cygwin can't load the original
+DLL at that same address in the child, the fork() call has to fail.
+</para>
+</listitem>
+<listitem>
+<para>File access problems.</para>
+<para>Some programs (e.g., virus scanners with on-access scanning) scan or
+otherwise operate on every file accessed by all the other software running on
+your computer.  In some cases they may retain an open handle on the file even
+after the software that is really using the file has closed it.  This has been
+known to cause operations such as deletes, renames and moves to fail with
+access denied errors.  In extreme cases it has been known for scanners to leak
+file handles, leading to kernel memory starvation.
+</para>
+</listitem>
+<listitem>
+<para>Networking issues</para>
+<para>Firewall software sometimes gets a bit funny about Cygwin.  It's not
+currently understood why; Cygwin only uses the standard Winsock2 API, but
+perhaps in some less-commonly used fashion that doesn't get as well tested
+by the publishers of firewalls.  Symptoms include mysterious failures to
+connect, or corruption of network data being sent or received.</para>
+</listitem>
+<listitem>
+<para>Memory and/or handle leaks</para>
+<para>Some applications that hook into the Windows operating system exhibit
+bugs when interacting with Cygwin that cause them to leak allocated memory
+or other system resources.  Symptoms include complaints about out-of-memory
+errors and even virtual memory exhaustion dialog boxes from the O/S; it is
+often possible to see the excess memory allocation using a tool such as
+Task Manager or Sysinternals' Process Explorer, although interpreting the
+statistics they present is not always straightforward owing to complications
+such as virtual memory paging and file caching.</para>
+</listitem>
+</itemizedlist></para>
+</answer></qandaentry>
diff -p -N -d -r -U2 winsup-src-20071227/cygwin-snapshot-20071227-1/winsup/utils/bloda.cc winsup-src-20071230/cygwin-snapshot-20071230-1/winsup/utils/bloda.cc
--- winsup-src-20071227/cygwin-snapshot-20071227-1/winsup/utils/bloda.cc	2007-12-21 15:05:57.000000000 +0000
+++ winsup-src-20071230/cygwin-snapshot-20071230-1/winsup/utils/bloda.cc	2007-12-30 22:07:17.000000000 +0000
@@ -42,4 +42,9 @@
     Windows Defender 
     Embassy Trust Suite fingerprint reader software containing wxvault.dll
+    ByteMobile laptop optimization client
+
+  A live version is now being maintained in the Cygwin FAQ, at
+    http://cygwin.com/faq/faq.using.html#faq.using.bloda
+
 */
 
@@ -48,5 +53,6 @@ enum bad_app
   SONIC,    NORTON,  MACAFFEE,    SYMANTEC,
   LOGITECH, KERIO,   AGNITUM,     ZONEALARM,
-  IOLO,     LANDESK, WINDEFENDER, EMBASSYTS
+  IOLO,     LANDESK, WINDEFENDER, EMBASSYTS,
+  BYTEMOBILE
 };
 
@@ -79,4 +85,5 @@ static const struct bad_app_det dodgy_ap
   { PROCESSNAME, "LVPrcSrv.exe",                                                 LOGITECH   },
   { FILENAME,    "%programfiles%\\common files\\logitech\\lvmvfm\\LVPrcSrv.exe", LOGITECH   },
+  { FILENAME,    "%windir%\\System32\\bmnet.dll",                                BYTEMOBILE },
 }; 
 
@@ -97,4 +104,5 @@ static struct bad_app_info big_list_of_d
   { WINDEFENDER, "Windows Defender"                                                       },
   { EMBASSYTS,   "Embassy Trust Suite fingerprint reader software containing wxvault.dll" },
+  { BYTEMOBILE,  "ByteMobile laptop optimization client"                                  },
 };