X-Spam-Check-By: sourceware.org Message-ID: <44F74434.E6E9C15C@dessent.net> Date: Thu, 31 Aug 2006 13:19:00 -0700 From: Brian Dessent X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: 1.5.21: fork in find/ls failing, simple test case References: <7 DOT 0 DOT 1 DOT 0 DOT 2 DOT 20060831082229 DOT 0234b668 AT crosstest DOT com> <004b01c6cd18$2d4bf660$a501a8c0 AT CAM DOT ARTIMI DOT COM> <6087159 DOT post AT talk DOT nabble DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com John Hartman wrote: > Okay, when I stopped the 'Logitech Process Monitor' service the problem goes > away. Thanks for the quick diagnosis. > > I rebased the camera dlls but that does not fix this problem. > > Can you tell me what the root cause is? > > Is there any way to prevent this problem? I.e., the problem of "foreign" > dlls causing cygwin forks to fail? It's crappy coding on the part of the Logitech module. Ross Ridge gives a convincing argument for what's going on: . More info on the loader lock issue is in this paper: . Now if only someone could forward these clues to the idiots that wrote that Logitech crapware, it would save a whole lot of frustration. Brian -- 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/