public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: marco atzeri <marco.atzeri@gmail.com>
To: Tassilo Philipp <tphilipp@potion-studios.com>
Cc: cygwin@cygwin.com
Subject: Re: more "address space needed ... is already occupied" problems (with snapshot of 2012-02-20)
Date: Thu, 23 Feb 2012 05:18:00 -0000	[thread overview]
Message-ID: <CAB8Xom8_toaEuW=M4Gd7bBvwEZ7GbjSwdpsCp-U3RPTgjHYEyw@mail.gmail.com> (raw)
In-Reply-To: <20120222223256.90d4fc28.tphilipp@potion-studios.com>

On Thu, Feb 23, 2012 at 5:32 AM, Tassilo Philipp  wrote:
> Doesn't do anything, and believe me, I tried that probably 50 times in all kinds of combinations...

do not top post please.

From where this "etc.so" is coming for ?
If it is something that you just built, than you should add all your
dll / so files to the rebase list using the "-T" option

rebaseall [-b BaseAddress] [-o Offset] [-s DllSuffix] [-T FileList |
-] [-4|-8] [-v}

so something like

find you_build_tree -name "*.so" > /tmp/rebase_list
find you_build_tree -name "*.dll" >> /tmp/rebase_list

and from dash
rebaseall -T /tmp/rebase_list

>
>
> On Thu, 23 Feb 2012 04:03:45 +0100
> marco atzeri  wrote:
>
>> On Thu, Feb 23, 2012 at 2:29 AM, Tassilo Philipp  wrote:
>> > Hello ml,
>> >
>> > I recently ran into many problems using rake to build a few of my projects, whenever rake calls itself recursively (for subprojects, etc. as in a typical make-style build tool setup). It's very random - sometimes I get a single error, sometimes nothing, but most of the time it sits there and prints the following until I kill the build:
>> >
>> >     17 [main] ruby 1028 child_info_fork::abort: address space needed by 'etc.so' (0x360000) is already occupied
>> >      1 [main] ruby 2076 child_info_fork::abort: address space needed by 'etc.so' (0x360000) is already occupied
>> >      1 [main] ruby 2128 child_info_fork::abort: address space needed by 'etc.so' (0x360000) is already occupied
>> >     ....
>> >
>> > I checked the mailing list and found all kind of infos about similar problem, but none of the solutions worked for me. What I - unsuccessfully - tried so far:
>> >
>> > - using the snapshot of feb 9, 2012 (which contains a fix by Corinna, that apparently solved a very similar problem pointed out a few days ago)
>> > - using latest snapshot of feb 20, 2012
>> > - using cygwin 1.7.10 and 1.7.9
>> > - playing around with rebaseall and peflagsall, with and without rebooting the machine
>> > - using ruby 1.8.7 as it is available via setup.exe
>> > - using self-built version of llatest release of ruby 1.9.3
>> > - wiping cygwin off my machine and reinstalling a mint version
>> > - many different combinations of the above
>> >
>> > So well, I guess 'm stuck. Any ideas?
>>
>> rebaseall ?
>> That is the standard solution for fork problem.
>> http://cygwin.com/faq-nochunks.html#faq.using.fixing-fork-failures
>>
>> It is likely needed any time you install a different cygwin version
>> including snapshots
>> or upgrade any other packages.
>>
>> Regards
>> Marco
>>
>> --
>> 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:[~2012-02-23  5:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-23  1:29 Tassilo Philipp
2012-02-23  3:04 ` marco atzeri
2012-02-23  4:33   ` Tassilo Philipp
2012-02-23  5:18     ` marco atzeri [this message]
2012-02-23 14:35       ` Tassilo Philipp
2012-02-23 14:48         ` marco atzeri
2012-02-23 14:55           ` Tassilo Philipp
2012-02-23  8:31     ` Corinna Vinschen
2012-02-23 23:24       ` Michael Lutz
2012-02-24  0:50         ` Tassilo Philipp
2012-02-24  2:25           ` marco atzeri
2012-02-24  8:08             ` Tassilo Philipp
2012-02-24  8:21               ` Corinna Vinschen
2012-02-24 19:13                 ` Tassilo Philipp
2012-02-24 12:32             ` Michael Lutz
2012-02-24 13:25               ` marco atzeri

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='CAB8Xom8_toaEuW=M4Gd7bBvwEZ7GbjSwdpsCp-U3RPTgjHYEyw@mail.gmail.com' \
    --to=marco.atzeri@gmail.com \
    --cc=cygwin@cygwin.com \
    --cc=tphilipp@potion-studios.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).