This is the mail archive of the
mailing list for the Cygwin project.
Re: bzr problem
- From: Achim Gratz <Stromeko at nexgo dot de>
- To: cygwin at cygwin dot com
- Date: Tue, 16 Jul 2013 07:10:03 +0200
- Subject: Re: bzr problem
- References: <b4m4nc1emxb dot fsf at jpl dot org> <87ppunbnae dot fsf at Rainer dot invalid> <b4mvc4bb7kp dot fsf at jpl dot org>
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.
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Waldorf Blofeld:
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple