From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: cygdll 3.3.4 breaks cygpath.exe. mistyped commands result in fork bomb
Date: Fri, 29 Apr 2022 17:41:54 -0400 [thread overview]
Message-ID: <66da7151-7621-028f-280e-7e7e355c3526@cornell.edu> (raw)
In-Reply-To: <2044845458.1632378.1651256726074@mail.yahoo.com>
On 4/29/2022 2:25 PM, matthew patton via Cygwin wrote:
> --- Process 25852 loaded C:\Program Files\SentinelOne\Sentinel Agent 21.7.4.1043\InProcessClient64.dll at 00007fff9d480000
This looks like the problem that was reported here:
https://cygwin.com/pipermail/cygwin/2022-February/250782.html
Can you try the suggestions I made in my reply
https://cygwin.com/pipermail/cygwin/2022-February/250790.html ?
Ken
next prev parent reply other threads:[~2022-04-29 21:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <945683463.1480145.1651191729148.ref@mail.yahoo.com>
2022-04-29 0:22 ` matthew patton
2022-04-29 9:04 ` Takashi Yano
2022-04-29 18:25 ` matthew patton
2022-04-29 18:59 ` matthew patton
2022-04-29 21:41 ` Ken Brown [this message]
2022-04-30 1:20 ` matthew patton
2022-05-04 16:50 ` matthew patton
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=66da7151-7621-028f-280e-7e7e355c3526@cornell.edu \
--to=kbrown@cornell.edu \
--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).