From: matthew patton <pattonme@yahoo.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>, Ken Brown <kbrown@cornell.edu>
Subject: Re: cygdll 3.3.4 breaks cygpath.exe. mistyped commands result in fork bomb
Date: Wed, 4 May 2022 16:50:34 +0000 (UTC) [thread overview]
Message-ID: <1664612404.2548128.1651683034295@mail.yahoo.com> (raw)
In-Reply-To: <1021087702.1698957.1651281614665@mail.yahoo.com>
The fork() bomb is still a problem with 3.3.4 but it's "benign" under <=3.2.0 because a Ctrl-C reaps the call stack. Something changed significantly between how processes are spawned apparently.
But the CAUSE of the fork() bomb was the combined use of CYGWIN_NOWINPATH=1 and this fragment in my .bashrc
function command_not_found_handle() { cmd.exe /D /C "$@"; }
It now reads:[ -z "${CYGWIN_NOWINPATH+X}" ] && is_exec cmd.exe && function command_not_found_handle() { cmd.exe /D /C "$@"; }
On Friday, April 29, 2022, 09:20:14 PM EDT, matthew patton <pattonme@yahoo.com> wrote:
> Can you try the suggestions I made in my reply https://cygwin.com/pipermail/cygwin/2022-February/250790.html ?
sorry, no. Even though I have Admin I am unable to override this. Please note that all previous versions of cygwin1.dll (<3.3.3) are not interfered with. Though if this is indeed Sentinel, it does seem to *sporadically* kill threads launched under strace regardless of cygwin DLL version all the way back to 3.1.7.
prev parent reply other threads:[~2022-05-04 16:50 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
2022-04-30 1:20 ` matthew patton
2022-05-04 16:50 ` matthew patton [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=1664612404.2548128.1651683034295@mail.yahoo.com \
--to=pattonme@yahoo.com \
--cc=cygwin@cygwin.com \
--cc=kbrown@cornell.edu \
/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).