public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: unison-2.48 build fails with latest ocaml and flexdll (attn: Achim)
Date: Mon, 03 Apr 2017 06:23:00 -0000	[thread overview]
Message-ID: <87h926m2ll.fsf@Rainer.invalid> (raw)
In-Reply-To: <841a950b-57dd-337f-4eb9-f76f053f0c06@cygwin.com> (Yaakov	Selkowitz's message of "Sun, 2 Apr 2017 21:23:15 -0500")

Yaakov Selkowitz writes:
> Achim, I think /usr/lib/ocaml needs to be ignored by autorebase;
> flexlink'ed DLLs are loaded very differently, and rebasing seems to
> break them.

I will be on a business trip for the rest of the week.  I can look at
excepting them, but I'd rather introduce a more general mechanism for
such things, I'll have to think about that.

The question is however if these actually work when they're not rebased
while some other library occupies their address space.  I suspect that'd
fail unless they are ASLR enabled.  Plus we need to make sure they don't
slip into the rebase space and block another Cygwin DLL trying to load
later.  Can somebody please test that?

While on the topic of ASLR, I've been experimenting with generally
making all (or most) Cygwin DLL ASLR enabled and avoid rebasing
altogether (that was triggered by some 32bit machine that I couldn't
switch over to a 3GB user VM for some reason).  It seems like that
should work, although it's unclear which subset of libraries must load
to fixed addresses (rebased or not).  Also, I'm not quite certain which
address space ASLR will use and if there's a "safe" space that it will
never occupy.  Unfortunately I haven't had much time to spend on that,
so if anybody feels inclined to try it I'll see if I can put something
into autorebase to support it.


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

Waldorf MIDI Implementation & additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs

  reply	other threads:[~2017-04-03  6:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-21 19:17 unison-2.48 build fails with latest ocaml and flexdll Andrew Schulman
2016-04-26 19:47 ` unison-2.48 build fails with latest ocaml and flexdll (ping: Yaakov, Damien) Andrew Schulman
2016-04-26 20:16   ` Achim Gratz
2016-04-27  9:16     ` Andrew Schulman
2016-04-27 11:16       ` Achim Gratz
2016-04-28  8:03   ` Marco Atzeri
2016-04-29 16:03     ` Andrew Schulman
2016-04-29 19:32       ` Mark Geisert
2016-04-29 19:43         ` Mark Geisert
2016-04-30 11:54         ` Andrew Schulman
2017-02-24 18:15           ` Andrew Schulman
2017-03-27 21:50             ` Yaakov Selkowitz
2017-03-31 17:00               ` Andrew Schulman
2017-04-03  2:23                 ` unison-2.48 build fails with latest ocaml and flexdll (attn: Achim) Yaakov Selkowitz
2017-04-03  6:23                   ` Achim Gratz [this message]
2017-04-08 17:42                     ` Achim Gratz
2017-04-03 17:12                   ` Andrew Schulman
2017-04-03 17:23                     ` Yaakov Selkowitz

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=87h926m2ll.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=cygwin-apps@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).