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 07:05:00 -0000	[thread overview]
Message-ID: <871u6z5bv8.fsf@Rainer.invalid> (raw)
In-Reply-To: <b4mvc4bb7kp.fsf@jpl.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.


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

  reply	other threads:[~2013-07-16  5:10 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 [this message]
2013-07-16 11:35       ` Katsumi Yamaoka
2013-07-16 18:47         ` Achim Gratz
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=871u6z5bv8.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).