public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: bzr problem
Date: Tue, 16 Jul 2013 18:47:00 -0000	[thread overview]
Message-ID: <87vc4a1k22.fsf@Rainer.invalid> (raw)
In-Reply-To: <b4ma9lm3k79.fsf@jpl.org>

Katsumi Yamaoka writes:
> BTW, when I run `bzr update' for the Emacs trunk, it shows a warning
> that varies like:
>
> 0 [main] python2.7 1300 child_info_fork::abort: unable to remap\
> _ARC4.dll to same address as parent (0xBE0000) - try running rebaseall
> 0 [main] python2.7 4180 child_info_fork::abort: address space needed by\
>  '_socket.dll' (0x860000) is already occupied
> 0 [main] python2.7 8072 child_info_fork::abort: address space needed by\
>  'operator.dll' (0x3D0000) is already occupied

What apparently happens is that the DLL gets originally loaded onto a
low address, presumably due to something intercepting the loader, then
when the process forks that address is already in use so the DLL can't
be mapped to that address in the process image.  This has all the
fingerprints of a "real-time" / behavioural virus scanner, so you might
want to investigate whether you can exclude the Cygwin install folder
from this.  If that's not possible to set up, you can sometimes move the
Cygwin installation into a directory tree that already is excluded
(often %PROGRAMFILES% is treated differently than other tress, etc.).

> rebaseall_log.txt shows that those DLLs were rebased into:
>
> /usr/lib/python2.7/site-packages/Crypto/Cipher/_ARC4.dll:\
>  new base = 36df0000, new size = 10000
> /usr/lib/python2.7/lib-dynload/_socket.dll:\
>  new base = 37170000, new size = 20000
> /usr/lib/python2.7/lib-dynload/operator.dll:\
>  new base = 36f90000, new size = 10000
>
> As for "_ARC4.dll", how does "36df0000" mean "0xBE0000"?

Not at all: the DLL simply doesn't get loaded where it has been rebased
to.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds


--
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-16 17:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-11  7:28 Katsumi Yamaoka
2013-07-12  0:59 ` Ken Brown
2013-07-12  3:17   ` Katsumi Yamaoka
2013-07-12  3:48   ` Katsumi Yamaoka
2013-07-12 19:23 ` Achim Gratz
2013-07-16  5:10   ` Katsumi Yamaoka
2013-07-16  7:05     ` Achim Gratz
2013-07-16 11:35       ` Katsumi Yamaoka
2013-07-16 18:47         ` Achim Gratz [this message]
2013-07-18  9:00           ` Katsumi Yamaoka

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=87vc4a1k22.fsf@Rainer.invalid \
    --to=stromeko@nexgo.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).