public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ariel Burbaickij <ariel.burbaickij@gmail.com>
To: cygwin@cygwin.com
Subject: Re: child (xterm) fork failure as it loads to different address
Date: Mon, 29 Jul 2013 12:32:00 -0000	[thread overview]
Message-ID: <CANeJNHrZdry8r0hFU-+3AhCocL9TDU4Mr-vWL8xmBn228aSWWg@mail.gmail.com> (raw)
In-Reply-To: <51F65369.9020001@gmail.com>

OK, thank, you, so usual suspects. Now, removing, antivirus and stuff
will not be possible in this particular environment but adjustments in
the configuration are well possible, provided I will be able to prove
to administrators that troubles, indeed, stem from antivirus and co.
Now, I see in the FAQ in 4.42 section that these troubles were traced
and attributed to antiviri programs. Any more details about how they
were traced exactly, so that I can re-trace them too and provide a
proof, if needed? Now, this is for one thing. Another one, is the
possibility to run Windows 7 (in my case) or any Windows  OS, down to
and including NT in POSIX-compatible "mode". Is this step expected to
solve or at least alleviate all or at least some the troubles about
the square peg of fork() into the round whole of Windows?

On Mon, Jul 29, 2013 at 1:35 PM, marco atzeri <marco.atzeri@gmail.com> wrote:
> Il 7/29/2013 10:10 AM, Ariel Burbaickij ha scritto:
>
>> Hello group,
>> I have a fresh installation of cygwin/ (cygcheck returns following for
>> cygwin1.dll: cygwin1.dll - os=4.0 img=1.0 sys=4.0 "cygwin1.dll" v0.0
>> ts=2013-07-22 16:06)/cygwin-X (1.14.2-1 built 2013-07-08)  and
>> following happens:
>> upon attempt to execute startxwin.exe  get following error, while
>> startxwin attempt to execute xterm:
>>
>>   xterm 5508 child_info_fork::abort: C:\nobackup\cygwin\bin\cygz.dll:
>> Loaded to different address: parent(0x320000) != child(0x3B0000)
>> xterm: Error 29, errno 11: Resource temporarily unavailable
>> Reason: spawn: fork() failed
>>
>>
>> while it is clear what happens, what is not clear is how to resolve
>> it, so that it does not happen anymore?
>
>
> http://cygwin.com/faq.html#faq.using.fixing-fork-failures
>
>>
>> /wbr
>> Ariel Burbaickij
>>
>> --
>
>
> otherwise, follow the guideline:
>>
>> Problem reports:       http://cygwin.com/problems.html
>
>
>
>
> --
> 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
>

--
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:[~2013-07-29 12:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-29 11:06 Ariel Burbaickij
2013-07-29 12:19 ` marco atzeri
2013-07-29 12:32   ` Ariel Burbaickij [this message]
2013-07-29 13:43     ` Ryan Johnson
2013-07-29 13:48       ` Corinna Vinschen
2013-07-29 14:17       ` Ariel Burbaickij
2013-07-29 14:33       ` Ariel Burbaickij

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=CANeJNHrZdry8r0hFU-+3AhCocL9TDU4Mr-vWL8xmBn228aSWWg@mail.gmail.com \
    --to=ariel.burbaickij@gmail.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).