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
<[email protected]> 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.
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation: https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
