public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* Problem forking from Zsh under 1.7 when installed under UNC path
@ 2012-07-02 13:24 Nikolai Weibull
  2012-07-02 14:20 ` Corinna Vinschen
  0 siblings, 1 reply; 3+ messages in thread
From: Nikolai Weibull @ 2012-07-02 13:24 UTC (permalink / raw)
  To: cygwin

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

I have installed Cygwin under the path \\Filer\Programs\Cygwin.
MODULE_PATH in Zsh is /usr/lib/zsh/4.3.11.

The modules are loaded fine inside Zsh itself, but can’t be mapped
over into the fork properly, it seems.

This occurred when I upgraded Cygwin from 1.5 to 1.7.  Zsh was also
upgraded from 4.3.11 to 4.3.12 at the same time, but was since
downgraded to exclude any changes that may have occurred in Zsh
between 4.3.11 and 4.3.12.

Note that running “ls” from Bash works fine, as it doesn’t have
loadable modules.

Mapping \\Filer\Programs\Cygwin to a drive and then running Zsh from
there works fine, so it seems that the issue is completely isolated to
that of the UNC path to the module not being saved/used correctly.

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Problem forking from Zsh under 1.7 when installed under UNC path
  2012-07-02 13:24 Problem forking from Zsh under 1.7 when installed under UNC path Nikolai Weibull
@ 2012-07-02 14:20 ` Corinna Vinschen
  2012-07-09 13:09   ` Nikolai Weibull
  0 siblings, 1 reply; 3+ messages in thread
From: Corinna Vinschen @ 2012-07-02 14:20 UTC (permalink / raw)
  To: cygwin

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Problem forking from Zsh under 1.7 when installed under UNC path
  2012-07-02 14:20 ` Corinna Vinschen
@ 2012-07-09 13:09   ` Nikolai Weibull
  0 siblings, 0 replies; 3+ messages in thread
From: Nikolai Weibull @ 2012-07-09 13:09 UTC (permalink / raw)
  To: cygwin

On Mon, Jul 2, 2012 at 4:19 PM, Corinna Vinschen wrote:
> On Jul  2 15:24, Nikolai Weibull wrote:

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

Seems to work fine.

Thank you!

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2012-07-09 13:09 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-07-02 13:24 Problem forking from Zsh under 1.7 when installed under UNC path Nikolai Weibull
2012-07-02 14:20 ` Corinna Vinschen
2012-07-09 13:09   ` Nikolai Weibull

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