From: Ulli Horlacher <framstag@rus.uni-stuttgart.de>
To: cygwin@cygwin.com
Subject: Re: Perl child_info_fork runtime error
Date: Mon, 09 Jul 2018 00:41:00 -0000 [thread overview]
Message-ID: <20180709004148.GB3525@rus.uni-stuttgart.de> (raw)
In-Reply-To: <20180530105709.GA12768@rus.uni-stuttgart.de>
To resume my mail:
On Wed 2018-05-30 (12:57), Ulli Horlacher wrote:
>
> One of my Perl programs produces strange runtime errors on a Windows 7
> system (CYGWIN_NT-6.1 32bit) of my colleague:
>
> 0 [main] perl 4232 child_info_fork::abort: address space needed
> by 'Encode.dll' (0x370000) is already occupied
> Can't fork, trying again in 5 seconds at /client/bin/fexsend line 106.
> 1 [main] perl 7720 child_info_fork::abort: address space needed
> by 'Encode.dll' (0x370000) is already occupied
> Can't fork, trying again in 5 seconds at /client/bin/fexsend line 106.
> 1 [main] perl 5484 child_info_fork::abort: address space needed
> by 'Encode.dll' (0x370000) is already occupied
> Can't fork, trying again in 5 seconds at /client/bin/fexsend line 106.
>
The information above was wrong. My colleague is using a 64 bit Windows!
And he was using my 32 bit cygwin installation.
After I gave him a 64 bit cygwin for his 64 bit Windows there are no more
"child_info_fork" errors!
Sorry for the confusion, it was all my fault!
--
Ullrich Horlacher Server und Virtualisierung
Rechenzentrum TIK
Universitaet Stuttgart E-Mail: horlacher@tik.uni-stuttgart.de
Allmandring 30a Tel: ++49-711-68565868
70569 Stuttgart (Germany) WWW: http://www.tik.uni-stuttgart.de/
REF:<20180530105709.GA12768@rus.uni-stuttgart.de>
--
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
prev parent reply other threads:[~2018-07-09 0:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 11:59 Ulli Horlacher
2018-05-30 22:05 ` Achim Gratz
2018-06-04 9:23 ` Ulli Horlacher
2018-06-04 19:24 ` Achim Gratz
2018-06-06 15:31 ` Ulli Horlacher
2018-06-06 15:49 ` Marco Atzeri
2018-06-06 16:49 ` Ulli Horlacher
2018-07-09 0:41 ` Ulli Horlacher [this message]
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=20180709004148.GB3525@rus.uni-stuttgart.de \
--to=framstag@rus.uni-stuttgart.de \
--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).