public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Problem forking from Zsh under 1.7 when installed under UNC path
Date: Mon, 02 Jul 2012 14:20:00 -0000	[thread overview]
Message-ID: <20120702141927.GF19239@calimero.vinschen.de> (raw)
In-Reply-To: <CADdV=MvDgqQW15UyJnUavRJjXn8QZRVChz7Pcvmz6wrGQBxF2A@mail.gmail.com>

On Jul  2 15:24, Nikolai Weibull wrote:
> Hi!
> 
> I have come across a problem that occurs when Zsh (both 4.3.11 and
> 4.3.12) tries to fork when Cygwin (1.7) has been installed under a UNC
> path.  The problem occurs because Zsh has support for dynamically
> loaded modules.  When Zsh forks to run a process (like “ls”), Cygwin
> tries to map these modules (DLLs) into the new process, but somewhere
> along the line gets confused as to what passed was used to load the
> module:
> 
>       2 [main] zsh 8220 child_info_fork::abort: unable to map UNC\Filer\Programs
> \Cygwin\lib\zsh\4.3.11\zsh\parameter.dll, Win32 error 126
> compaudit:91: fork failed: resource temporarily unavailable
>       2 [main] zsh 4836 child_info_fork::abort: unable to map UNC\Filer\Programs
> \Cygwin\lib\zsh\4.3.11\zsh\zle.dll, Win32 error 126
> compinit:526: fork failed: resource temporarily unavailable

Thanks for the report.  That's certainly a bug in Cygwin.  I applied
a patch which is supposed to fix this issue.  Please test the next
developer snapshot from http://cygwin.com/snapshots/


Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
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

  reply	other threads:[~2012-07-02 14:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-02 13:24 Nikolai Weibull
2012-07-02 14:20 ` Corinna Vinschen [this message]
2012-07-09 13:09   ` Nikolai Weibull

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=20120702141927.GF19239@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --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).