From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: cygdll 3.3.4 breaks cygpath.exe. mistyped commands result in fork bomb
Date: Fri, 29 Apr 2022 18:04:14 +0900 [thread overview]
Message-ID: <20220429180414.b3a0572687203fda213f878d@nifty.ne.jp> (raw)
In-Reply-To: <945683463.1480145.1651191729148@mail.yahoo.com>
On Fri, 29 Apr 2022 00:22:09 +0000 (UTC)
matthew patton wrote:
> I had to revert to 3.3.3-1 to restore functionality.with 3.3.4 invoking cygpath would cause an Access Violation Exception (0x05) and kill the thread so that I couldn't even do a 'cygpath --help'
>
> All of a sudden I also am experiencing fork bombs if I type an invalid command. eg. type 'l' instead of 'ls' and ENTER, it spawns hundreds of 'bash.exe' processes. A half dozen 'pkill -9 bash.exe' heads off calamity.
That does not happen to me.
--
Takashi Yano <takashi.yano@nifty.ne.jp>
next prev parent reply other threads:[~2022-04-29 9:04 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 [this message]
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
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=20220429180414.b3a0572687203fda213f878d@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--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).