public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Hermann Kleier <hermann@kleier.net>
To: cygwin@cygwin.com
Subject: RE: _pinfo::dup_proc_pipe: DuplicateHandle failed
Date: Mon, 19 Jan 2009 02:50:00 -0000	[thread overview]
Message-ID: <21534876.post@talk.nabble.com> (raw)
In-Reply-To: <00c901c8bbff$287092e0$2708a8c0@CAM.ARTIMI.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/

  reply	other threads:[~2009-01-18 23:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-21 15:01 Relson, David
2008-05-21 16:20 ` Hugh Sasse
     [not found]   ` <91FA647A1A781F41BBB0359765C90C159AE3F4@mailsvr.orion-sys.com>
2008-05-22 11:30     ` Hugh Sasse
2008-05-22 11:48       ` Dave Korn
2009-01-19  2:50         ` Hermann Kleier [this message]
2011-02-16 11:30 Kaltenberger, Stefan
2011-02-16 16:33 ` Christopher Faylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=21534876.post@talk.nabble.com \
    --to=hermann@kleier.net \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).