public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: ld randomly assigns wrong user and group IDs to executable
Date: Tue, 26 Apr 2016 19:50:00 -0000	[thread overview]
Message-ID: <87h9eop30q.fsf@Rainer.invalid> (raw)
In-Reply-To: <imgvhbhlgq3unbgemhdqettdjq5d31v0bm@4ax.com> (Andrew Schulman's	message of "Tue, 26 Apr 2016 15:40:17 -0400")

Andrew Schulman writes:
> Seems to be a BLODA problem. The problem is inconsistent/intermittent, and
> happens only on one of my three Windows hosts. The bad machine has
> Symtantec Endpoint Protection running (I can't disable it), and
> CYGWIN=detect_bloda also finds C:\windows\system32\privman64.dll, the
> "BeyondTrust Power Broker for Windows DLL". Seems a likely suspect.

Endpoint protection places a DLL at the very end of the Cygwin rebase
area in my experience.  Look at /proc/self/maps and "rebase -si" if it's
consistent and what Cygwin library gets rebased there.  You might want
to change the rebase area dow to some lower address (you could edit it
in /usr/bin/rebaselst and trigger a full rebase as an experiment).


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

--
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:[~2016-04-26 19:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-22 18:08 Andrew Schulman
2016-04-22 19:28 ` Andrew Schulman
2016-04-26 19:46 ` Andrew Schulman
2016-04-26 19:50   ` Achim Gratz [this message]

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=87h9eop30q.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).