unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: 50666@debbugs.gnu.org
Subject: bug#50666: 28.0.50; Fix native compilation on Cygwin
Date: Thu, 23 Sep 2021 20:25:02 +0200	[thread overview]
Message-ID: <874kabrvy9.fsf@Rainer.invalid> (raw)
In-Reply-To: <9f20194e-b1ba-9417-4f18-caa1d80b5568@cornell.edu>

Eli Zaretskii writes:
> You mean, ASLR doesn't work with Cygwin because it must use the same
> address in the forked process?  But then why did Ken say that ASLR and
> High Entropy could solve the problem with the *.eln files -- isn't
> that the same problem?

It is, but on 64bit with the massive address space and high entropy
using most of it, it will often "just work" for quite some time.

> Sorry, I don't understand.  My suggestion was, if you need to make the
> *.eln files be marked as ASLR with High Entropy, to use a variable we
> have for this purpose, it will force the linker to produce *.eln files
> with these bits set in the PE+ header.  What other control do you need
> for your purposes, or what am I missing?

The control that Cygwin would need is an indication to whatever
generates the image base shifts for ASLR that it should not re-map an
image that is already in use elsewhere (maybe just in the same process
group).  ASLR already re-uses the address for the same image most of the
time (the exact behaviour is different across Windows versions), but
depending on circumstances outside your control it can suddenly decide
to use a different address.


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






  reply	other threads:[~2021-09-23 18:25 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-18 20:46 bug#50666: 28.0.50; Fix native compilation on Cygwin Ken Brown
2021-09-18 20:58 ` Ken Brown
2021-09-19  5:37   ` Eli Zaretskii
2021-09-19  7:00     ` ASSI
2021-09-19  7:08       ` Eli Zaretskii
2021-09-19 11:31         ` ASSI
2021-09-19 12:06           ` Eli Zaretskii
2021-09-19 12:37             ` Ken Brown
2021-09-19 13:41               ` Eli Zaretskii
2021-09-19 14:27                 ` Ken Brown
2021-09-19 15:28                   ` Eli Zaretskii
2021-09-19 16:17                     ` Ken Brown
2021-09-19 17:12                       ` Eli Zaretskii
2021-09-22 21:35                         ` Ken Brown
2021-09-23  7:42                           ` Eli Zaretskii
2021-09-23 14:20                             ` Ken Brown
2021-09-23 16:37                               ` Eli Zaretskii
2021-09-23 17:13                                 ` Ken Brown
2021-09-23 17:29                                   ` Eli Zaretskii
2021-09-23 17:49                                     ` Achim Gratz
2021-09-23 18:01                                       ` Eli Zaretskii
2021-09-23 18:25                                         ` Achim Gratz [this message]
2021-09-23 18:46                                           ` Eli Zaretskii
2021-10-28 22:22                                   ` Ken Brown
2021-10-29  5:54                                     ` Eli Zaretskii
2021-10-29 17:03                                       ` Ken Brown
2021-10-29 18:01                                         ` Eli Zaretskii
2021-10-29 18:12                                           ` Ken Brown
2021-10-31 20:22                                             ` Achim Gratz
2021-10-31 23:52                                               ` Ken Brown
2021-09-23 17:27                                 ` Achim Gratz
2021-09-23 17:48                                   ` Eli Zaretskii
2021-09-23 18:29                                     ` Achim Gratz
2021-09-23 18:57                                       ` Eli Zaretskii
2021-09-23 19:37                                       ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-24  6:11                                         ` ASSI
2021-09-24  7:13                                           ` Eli Zaretskii
2021-09-24  7:32                                           ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-24  9:05                                             ` ASSI
2021-09-24 10:48                                             ` Eli Zaretskii
2021-09-25 15:10                                               ` Eli Zaretskii
2021-09-23 19:11                             ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-23 19:21                               ` Eli Zaretskii
2021-09-24  6:04                               ` ASSI
2021-09-24  7:10                                 ` Eli Zaretskii
2021-09-24  7:26                                   ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-24 11:10                                     ` Eli Zaretskii
2021-09-24 12:49                                       ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-24  9:15                                   ` ASSI
2021-09-24 11:03                                     ` Eli Zaretskii
2021-09-19  5:32 ` Eli Zaretskii

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874kabrvy9.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=50666@debbugs.gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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