Re: cygin 3.6.2-1 under Win11 24H2: Cannot launch: no available terminals

2025-05-28 Thread Andrey Repin via Cygwin
Greetings, Robert Fensterman! > When I try to launch Cygwin 3.6.2-1 - be it from the taskbar shortcut, > double-clicking on mintty.exe, or running mintty.exe from CMD - I get an > error message: >> Error: Could not fork child process: There are no available terminals (-1) > The resulting window

Re: cygin 3.6.2-1 under Win11 24H2: Cannot launch: no available terminals

2025-05-28 Thread Robert Fensterman via Cygwin
/etc/shells: /bin/sh /bin/ash /bin/bash /bin/dash /bin/mksh /bin/pdksh /bin/posh /bin/tcsh /bin/zsh /usr/bin/sh /usr/bin/ash /usr/bin/bash /usr/bin/dash /usr/bin/mksh /usr/bin/pdksh /usr/bin/posh /usr/bin/tcsh /usr/bin/zsh getent passwd %USERNAME% is blank With cygwin 3.6.2-1, I can start bash d

Re: Crash or hang if SIGSEGV+SIGALRM are nested

2025-05-28 Thread Takashi Yano via Cygwin
On Wed, 28 May 2025 21:57:07 +0900 Takashi Yano wrote: > Hi Christian, > > On Mon, 19 May 2025 12:55:46 +0200 > Christian Franke wrote: > > The attached testcase was originally intended to investigate why a > > SIGSEGV from non-signal code could interrupt an already running signal > > handler. >

Re: Crash or hang if SIGSEGV+SIGALRM are nested

2025-05-28 Thread Takashi Yano via Cygwin
Hi Christian, On Mon, 19 May 2025 12:55:46 +0200 Christian Franke wrote: > The attached testcase was originally intended to investigate why a > SIGSEGV from non-signal code could interrupt an already running signal > handler. > https://sourceware.org/pipermail/cygwin-patches/2025q2/013703.html >