public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Tim McDaniel <tmcd@panix.com>
To: cygwin@cygwin.com
Subject: Re: Another BLODA with Cylance PROTECT? Can't rebase
Date: Tue, 25 Apr 2017 16:43:00 -0000	[thread overview]
Message-ID: <Pine.NEB.4.64.1704250004500.6548@panix3.panix.com> (raw)
In-Reply-To: <20170421115857.GC26611@calimero.vinschen.de>

On Fri, 21 Apr 2017, Corinna Vinschen <corinna-cygwin@cygwin.com> wrote:
> On Apr 19 14:25, Timothy McDaniel wrote:
>> $ ./0p_000_autorebase.dash
>> creating empty /var/cache/rebase/rebase_pkg
>>       0 [main] dash 12952 fork: child 12912 - died waiting for dll
>> loading, errno 11
>> /bin/rebaselst: 98: /bin/rebaselst: Cannot fork
>> $ ./base-files-mketc.sh
>>       0 [main] sh 13628 fork: child 10276 - died waiting for dll loading,
>> errno 11
>> ./base-files-mketc.sh: fork: retry: Resource temporarily unavailable
>> ...
>
> That's pretty bad, considering that ash only links against the Cygwin
> DLL itself.
>
>> Running /bin/rebaseall by hand, the old way, had no output and no
>> effect.
>
> No effect?  How do you know?

My apologies.  I later ran with the verbose option, letting it choose
an address, and later choosing a few myself.  There was output saying
that it was rebasing each package.  Instead of "no effect", I should
have written that the exact same error message came up when I tried to
run anything slightly complicated.  (Simple commands work, but
harmless-looking things like "time" and many pipes fail.)

> If you're sure Cylance PROTECT is the culprit,

I'm not.  It did not throw up any messages or log any events about
blocking anything.  It's just that most BLODA appears to be antivirus
systems, and it's the only substantial change that I know of in my
work systems.  (We're still on the same version of Windows.)


I have a little more information.  A co-worker told me that he uses
"Babun", http://babun.github.io/.  It's Cygwin, but with a larger
number of installed and configured packages and a moderately more
convenient control system.  I installed it and it works fine ... but
immeidately on installation, it's an old Cygwin.  (By defualt, each
day it auto-updates to the current Cygwin.)

     Jun 23  2015 libcygwin.a

For example, Perl there is 5.14.4, but the current Cygwin Perl is
5.24.1.  pcre is 8.36, versus current 8.40.3.  But, like I said, it
works.  If I update to the latest, though, it fails in exactly the
same way as a regular Cygwin installation.

So all I can say is that it seems that there was some change to
libcygwin.a some time in the last 2 years to which my system is
allergic for some reason, which is hardly any help.

But I don't know how to proceed further, except by letting this 2015
installation sit and never ever update it.  Or install a virtual
machine with disk sharing and try to do my occasional UNIXy work with
it.  Someone from the local support team has asked why I was asking
about Cygwin, and why I'm interested in "Running OSes on top of
OSes".  So I may have to go the VM route.

-- 
Tim McDaniel, tmcd@panix.com

--
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:[~2017-04-25  5:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-20 14:17 Timothy McDaniel
2017-04-21 17:40 ` Corinna Vinschen
2017-04-25 16:43   ` Tim McDaniel [this message]
2017-04-25 18:05     ` cyg Simple
2017-04-26  1:17     ` Brian Inglis
2017-05-24  3:44 Tim McDaniel
2017-05-24  7:43 ` Brian Inglis
2017-05-25 23:19   ` Tim McDaniel

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=Pine.NEB.4.64.1704250004500.6548@panix3.panix.com \
    --to=tmcd@panix.com \
    --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).