From: cgf AT bbc DOT com (Chris Faylor) Subject: Re: cygwin: Cygwin32: Catastrophic fail - unable to Create pinfo_mutex 28 Jul 1997 09:15:57 -0700 Approved: cygnus DOT gnu-win32 AT cygnus DOT com Distribution: cygnus Message-ID: References: <3 DOT 0 DOT 32 DOT 19970727183116 DOT 00bb3dd0 AT nuancecom DOT com> Reply-To: cgf AT bbc DOT com X-Newsreader: trn 4.0-test57 (27 Apr 97) Original-To: gnu-win32 AT cygnus DOT com X-Mailer: Perl5 Mail::Internet v1.28 Original-Sender: owner-gnu-win32 AT cygnus DOT com In article <3 DOT 0 DOT 32 DOT 19970727183116 DOT 00bb3dd0 AT nuancecom DOT com>, JP Shipherd wrote: >I recently had to reinstall NT. It now resides on the D drive and the gnu >tools continue to reside on the C drive. Ever since then, when doing makes >I often get: > >cygwin: Cygwin32: Catastrophic fail - unable to Create pinfo_mutex > >It then seems to continue on quite nicely. However, a little system memory >seems to be siphoned off after each of these messages which NT never >manages to get back, meaning I need to reboot periodically. > >Anyone know what causes this? I think there is a race of some kind in cygwin.dll which manifests as the inability to create a mutex which is used to lock accesses to the process table. I have not had any problems like this since switching to Sergey's cygwin.dll: http://www.lexa.ru/sos And, there are all sorts of other benefits to switch, too. -- http://www.bbc.com/ cgf AT bbc DOT com "Strange how unreal VMS=>UNIX Solutions Boston Business Computing the real can be." - For help on using this list (especially unsubscribing), send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help".