Re: W10 Mandatory ASLR default

00:36, Andreas Schiffler wrote: On 2/13/2018 11:17 PM, Thomas Wolff wrote: Am 14.02.2018 um 04:25 schrieb Brian Inglis: On 2018-02-12 21:58, Andreas Schiffler wrote: Found the workaround (read: not really a solution as it leaves the system vulnerable, but it unblocks cygwin) - Go to Windows De

Re: W10 Mandatory ASLR default

rsion 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\kernel] "MitigationOptions"=hex:00,01,21,00,00,00,00,00,00,00,00,00,00,00,00,00 On 2/13/2018 11:17 PM, Thomas Wolff wrote: Am 14.02.2018 um 04:25 schrieb Brian Inglis: On 2018-02-12 21:58, Andreas Schiff

Re: cygwin stopped working

k or do anything (see above). On 2/12/2018 8:49 AM, Jostein Berntsen wrote: On 11.02.18,17:16, Andreas Schiffler wrote: Thanks for the tip, but that didn't seem to have helped. The registry setting CYGWIN_NOWINPATH=1 did not seem to affect the environment as seen in bash. The variable see

Re: cygwin stopped working

distribution.  Rebooting is also suggested if you are unable to find another cygwin DLL. On 2/11/2018 2:42 AM, Doug Henderson wrote: On 11 February 2018 at 01:18, Andreas Schiffler wrote: Terminal (bash) fails with: Error: Could not fork child process: Resource temporarily unavailable (-1).

cygwin stopped working

Terminal (bash) fails with: Error: Could not fork child process: Resource temporarily unavailable (-1). DLL rebasing may be required; see 'rebaseall / rebase --help'. PC was rebooted and the cygwin was "refreshed". Installer (version 2.884, 32bit) fails with: Package: 0/Perpetual     0p_000_au

libtool quoting error

The libtool distributed with cygwin has a bug that prevents use in paths containing spaces. This was encountered when trying to build SDL2 on Windows (see http://bugzilla.libsdl.org/show_bug.cgi?id=1575 for details or repro). # Which release of libtool.m4 was used? macro_version=2.2.6 macro_rev