Brian.Kelly@empireblue.com wrote: > It would have been "nice" if there was an acknowledgement of this > problem (cygwin's or not) rather than attempted character assassinations. It has already been acknowledged several times over that it is not a problem of Cygwin's rather a problem of Windows. What else do you want? When you cluelessly continue to assert that it's a Cygwin memory leak is exactly where is leads down the path to character assassinations. (BTW: Ever think of replacing that Windows box with just a Linux box?) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/