X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:references
	:mime-version:content-type; q=dns; s=default; b=rm+KO/P/buqHT3vZ
	BkGv3CuniWhacmQwCkCDeF5H7riYP+qBNqEzvW6ySOM5cGDaOlY0urOr+8z3qHna
	fiuYX4yGHt2jsJqC4civsEc2zIYQo0ZbDOahbzifCY1/BIV4y/HMWzEEDq54fXto
	2E8hsFeZ+ltnEy1aIlXETm3StFA=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:references
	:mime-version:content-type; s=default; bh=n+unOF4js/KNsEIddWXTyD
	QSaDw=; b=BYT7JaPY/5LQyAI6Zd/r5ffcLkN2kc6G32h2Wn7zdXjxWVkKHtHQVn
	QInnoz6s4fHwdYj5ci9Zw39sILoLWGOjje2+iodCgS/tfrDCTWjUs14kOrbPHh3j
	hY1GpDwIRpS8SZ8M9xutU9bcQwzIdKn0KgSpscAvSL1sa36H4sbbo=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
X-Spam-SWARE-Status:	No, score=-1.7 required=5.0 tests=AWL,BAYES_50,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,RDNS_NONE,SPF_HELO_PASS,SPF_PASS,TW_BZ autolearn=no version=3.3.1
To:	cygwin AT cygwin DOT com
From:	Achim Gratz <Stromeko AT nexgo DOT de>
Subject:	Re: bzr problem
Date:	Tue, 16 Jul 2013 07:10:03 +0200
Lines:	24
Message-ID:	<871u6z5bv8.fsf@Rainer.invalid>
References:	<b4m4nc1emxb DOT fsf AT jpl DOT org> <87ppunbnae DOT fsf AT Rainer DOT invalid> <b4mvc4bb7kp DOT fsf AT jpl DOT org>
Mime-Version:	1.0
User-Agent:	Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)

Katsumi Yamaoka writes:
>> I'd venture to guess that the DLL(s) in question belong to a Python
>> package.  If so, does the rebaseall script you are using look at those
>> libraries at all?
>
> As far as I can observe, those DLLs are listed in TEMP/rebase.lst
> (that rebaseall temporarily generates), and `rebaseall -v' shows
> that they are processed by `rebase'.  Thanks.

You could dump the contents of the rebase database then and check what
the base address for this library is supposed to be.  Chances are that
it is very much higher than what your example of a fork fail shows.  In
my experience, such low base addresses indicate BLODA; however if a
library is indeed rebased into this region it has almost zero chances of
correctly forking in that address range.


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

Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables


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

- Raw text -