From: Denis Excoffier <cygwin@Denis-Excoffier.org>
To: cygwin@cygwin.com
Subject: Re: cygwin-1.7.10-1 fork - address space needed by ... already in use
Date: Fri, 16 Mar 2012 18:41:00 -0000 [thread overview]
Message-ID: <AEA15545-E9EE-43C0-A8BD-545DC4F65F14@Denis-Excoffier.org> (raw)
In-Reply-To: <20120316171426.GA20243@ednor.casa.cgf.cx>
[-- Attachment #1: Type: text/plain, Size: 3158 bytes --]
On 2012-03-16 18:14, Christopher Faylor wrote:
> On Fri, Mar 09, 2012 at 10:48:30AM -0500, Christopher Faylor wrote:
>> On Thu, Mar 08, 2012 at 10:55:35AM +0100, Corinna Vinschen wrote:
>>> On Mar 8 09:50, Denis Excoffier wrote:
>>>> On Wed, Mar 07, 2012 at 06:47:49PM +0100, Corinna Vinschen wrote:
>>>>>> Hi Denis,
>>>>>>
>>>>>> can you please test this again using the latest developer snapshot or
>>>>>> the current from CVS if you build Cygwin by yourself? It provides a bit
>>>>>> more information to find the reason for the permission denied error in
>>>>>> _pinfo::dup_proc_pipe.
>>>> Thank you cgf (the committer and snapshot maker at least).
>>>>>>
>>>>>> In theory, the user should have permissions to duplicate handles into
>>>>>> every own process, if the handle has been opened with these permissions,
>>>>>> so it's quite interesting to find the reason.
>>>>>>
>>>>
>>>> After about 3 hours of exercising the new snapshot (and shaking it a
>>>> little), i met the "something failed" instance only twice:
>>>>
>>>> 1 [main] tcsh 7648! _pinfo::dup_proc_pipe: (child_info_spawn::worker) process synchronization failed for pid 7648/0x754, wr_proc_pipe 0x0 vs. 0x764: DuplicateHandle winerr 5, WFSO returned 258, Win32 error 5
>>>> 503 [main] tcsh 6148! _pinfo::dup_proc_pipe: (child_info_spawn::worker) process synchronization failed for pid 6148/0x758, wr_proc_pipe 0x0 vs. 0x768: DuplicateHandle winerr 5, WFSO returned 258, Win32 error 5
>>>>
>>>> I continue, of course.
>>>
>>> Thanks, I don't think it's necessary to try further. What this shows is
>>> that the process handle returned by the call to CreateProcess sometimes,
>>> for some reason, does not allow handle duplication. That's weird.
>>
>> I have a vague idea about why this is happening. I'll look into it within
>> the next 48 hours.
>
> My vague idea about this proved to be incorrect. I did manage to make a
> royal mess of the exec synchronization code before I figured that out
> though so at least that's something.
>
> Denis, did you see this while running the STC in
>
> http://cygwin.com/ml/cygwin/2012-02/msg00187.html
>
> ?
No i didn't. This STC was another (probably independent, but much more important)
problem, solved by Corinna in February. For the moment i could not find
any reproducible scheme that leads to "process synchronization failed".
However, a full night of various compilations (using make -j 3) produces about
a dozen of such messages (using make with no -j produces no message, that's
all what i know for the moment).
>
> Also, I checked back through the archives but didn't see any cygcheck
> output from you. Maybe I just missed it but would you mind sending it
> here?
Included cygcheck.out and cygcheck.err (from last Tuesday).
Other problems i still have not fully reported:
- ldd produces "??? => ???" on some DLLs (/usr/bin/cygoctave-1.dll produces 6 such lines)
- strace produces "too many environment variables" always
- sometimes a process get frozen (not reproducible), if i kill it, the
killing process also gets frozen
Denis Excoffier.
[-- Attachment #2: cygcheck.out --]
[-- Type: application/octet-stream, Size: 319031 bytes --]
[-- Attachment #3: Type: text/plain, Size: 1 bytes --]
[-- Attachment #4: cygcheck.err --]
[-- Type: application/octet-stream, Size: 94 bytes --]
/usr/bin/cygrunsrv: warning: OpenService failed for 'TapiSrv': Win32 error 5
Accès refusé.
[-- Attachment #5: Type: text/plain, Size: 3 bytes --]
[-- Attachment #6: Type: text/plain, Size: 218 bytes --]
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2012-03-16 18:41 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 15:00 Scott M. Ballew
2012-02-07 15:44 ` Denis Excoffier
2012-02-07 16:15 ` Corinna Vinschen
2012-02-07 16:47 ` Ryan Johnson
2012-02-07 22:48 ` Denis Excoffier
2012-02-08 9:03 ` Corinna Vinschen
2012-02-08 9:08 ` Denis Excoffier
2012-02-08 9:27 ` Corinna Vinschen
2012-02-08 10:23 ` Denis Excoffier
2012-02-08 12:33 ` Earnie Boyd
2012-02-08 13:00 ` Corinna Vinschen
2012-02-08 13:35 ` Corinna Vinschen
2012-02-08 14:25 ` Heiko Elger
2012-02-08 14:37 ` Corinna Vinschen
2012-03-04 17:23 ` Corinna Vinschen
2012-02-08 14:55 ` Denis Excoffier
2012-02-08 15:06 ` Heiko Elger
2012-02-08 15:35 ` Denis Excoffier
2012-02-08 15:16 ` Corinna Vinschen
2012-02-09 11:07 ` Corinna Vinschen
2012-02-09 13:40 ` Denis Excoffier
2012-02-09 14:44 ` Corinna Vinschen
2012-02-10 12:35 ` Andrey Repin
2012-02-13 13:48 ` Scott M. Ballew
2012-02-23 16:30 ` Richard Gribble
2012-02-23 17:23 ` Corinna Vinschen
2012-02-09 14:44 ` Denis Excoffier
2012-03-04 17:22 ` Corinna Vinschen
2012-03-05 7:09 ` Denis Excoffier
2012-03-05 10:00 ` Corinna Vinschen
2012-03-05 12:02 ` Denis Excoffier
2012-03-05 12:15 ` Corinna Vinschen
2012-03-07 17:48 ` Corinna Vinschen
2012-03-08 8:50 ` Denis Excoffier
2012-03-08 9:56 ` Corinna Vinschen
2012-03-09 15:48 ` Christopher Faylor
2012-03-16 17:14 ` Christopher Faylor
2012-03-16 18:41 ` Denis Excoffier [this message]
2012-03-19 20:55 ` Christopher Faylor
2012-03-20 5:11 ` 2012-03-19 snapshot problematic (was Re: cygwin-1.7.10-1 fork - address space needed by ... already in use) Christopher Faylor
2012-03-20 23:56 ` All clear (was Re: 2012-03-19 snapshot problematic (was Re: cygwin-1.7.10-1 fork - address space needed by ... already in use)) Christopher Faylor
2012-03-21 4:41 ` marco atzeri
2012-03-21 5:44 ` marco atzeri
2012-03-21 7:11 ` Denis Excoffier
2012-03-22 4:38 ` Christopher Faylor
2012-03-22 6:57 ` Denis Excoffier
2012-03-22 13:29 ` Christopher Faylor
2012-03-22 14:38 ` Denis Excoffier
2012-03-22 15:13 ` Christopher Faylor
2012-03-22 15:33 ` Karl M
2012-03-22 15:36 ` Karl M
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=AEA15545-E9EE-43C0-A8BD-545DC4F65F14@Denis-Excoffier.org \
--to=cygwin@denis-excoffier.org \
--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).