X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=2.6 required=5.0 tests=BAYES_50,DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: sourceware.org Message-ID: <21534876.post@talk.nabble.com> Date: Sun, 18 Jan 2009 15:52:44 -0800 (PST) From: Hermann Kleier To: cygwin AT cygwin DOT com Subject: RE: _pinfo::dup_proc_pipe: DuplicateHandle failed In-Reply-To: <00c901c8bbff$287092e0$2708a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <91FA647A1A781F41BBB0359765C90C159AE3D3 AT mailsvr DOT orion-sys DOT com> <00c901c8bbff$287092e0$2708a8c0 AT CAM DOT ARTIMI DOT COM> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 Hugh Sasse wrote on 22 May 2008 12:08: >> relsondt1--> ./hello.sh >> + Bcc +BccDos.cfg -c -Ic:/BC45/INCLUDE -D -oHELLO.OBJ HELLO.CPP >> 7 [main] bash 5564! _pinfo::dup_proc_pipe: DuplicateHandle failed, \ >> pid 5564, hProcess 0x6DD, wr_proc_pipe 0x750, Win32 error 6 > > That Win32 error looks more like it is to do with Windows than Cygwin > per se. So what is "Win32 error 6" http://msdn.microsoft.com/en-us/library/ms681382(VS.85).aspx ERROR_INVALID_HANDLE > which says there are problems with your registry if you get this. No, it's what you'd expect if you try and dup a handle that's already been closed - an indication that the child exited prematurely. This is one of those semi-generic fork failures that could be BLODA, but another possibility is that because this is a non-cygwin app being launched from cygwin, it might be pulling in a dll that causes a rebase conflict. Following the rebaseall procedure described in the "Usage:" section of /usr/share/doc/Cygwin/rebase-2.4.3.README might help as is, or it might be necessary to find a list of the dlls being pulled in by the borland compiler and rebase them too by adding a -T option pointing to a file that lists the (cygwin-style posix) paths to the BC45 dlls. We've got the same problem using BORLAND C 4.52. I tried the rebasing-procedure as described including the bc45 DLLs. But anyway, the problem persists. Ebereythiong worked fine with cygwin 1.5.19 and failed after upgrading to 1.5.25. After a couple of days of searching for a kludge, I'm really frustrated. There's a high timely pressure on the project. I'd like to downgrade to 1.5.19 just to get it running again. But where can we get precedent revisions? Or is there anything else that I could try? Hermann Kleier -- View this message in context: http://www.nabble.com/_pinfo%3A%3Adup_proc_pipe%3A-DuplicateHandle-failed-tp17367978p21534876.html Sent from the Cygwin list mailing list archive at Nabble.com. -- 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/