Re: lost signal

Roland Mainz via Cygwin wrote: On Fri, Mar 7, 2025 at 9:01 AM Takashi Yano via Cygwin wrote: On Fri, 7 Mar 2025 16:29:51 +0900 Takashi Yano wrote: On Wed, 5 Mar 2025 11:23:26 +0100 Christian Franke wrote: ... Unfortunately signals may be lost, a new testcase is attached: ... $ ./lostsig 116

Re: lost signal (was: cygwin 3.6.0: Signals may fail permanently if received after SIGSTOP)

On Fri, Mar 7, 2025 at 9:01 AM Takashi Yano via Cygwin wrote: > > On Fri, 7 Mar 2025 16:29:51 +0900 > Takashi Yano wrote: > > On Wed, 5 Mar 2025 11:23:26 +0100 > > Christian Franke wrote: > > > Takashi Yano via Cygwin wrote: > > > > On Mon, 24 Feb 2025 11:29:59 +0100 > > > > Christian Franke wrote

Re: lost signal (was: cygwin 3.6.0: Signals may fail permanently if received after SIGSTOP)

On Fri, Mar 7, 2025 at 8:29 AM Takashi Yano via Cygwin wrote: > On Wed, 5 Mar 2025 11:23:26 +0100 > Christian Franke wrote: [snip] > > A 'ps' is a second terminal then shows that the child process is still > > in S)topped state. 'kill -CONT ...' works to continue. > > > > If the testcase is assign

Re: lost signal (was: cygwin 3.6.0: Signals may fail permanently if received after SIGSTOP)

On Fri, 7 Mar 2025 16:29:51 +0900 Takashi Yano wrote: > On Wed, 5 Mar 2025 11:23:26 +0100 > Christian Franke wrote: > > Takashi Yano via Cygwin wrote: > > > On Mon, 24 Feb 2025 11:29:59 +0100 > > > Christian Franke wrote: > > >> Found with 'stress-ng --cpu-sched 1': > > >> > > >> Testcase (attached

Re: lost signal (was: cygwin 3.6.0: Signals may fail permanently if received after SIGSTOP)

On Wed, 5 Mar 2025 11:23:26 +0100 Christian Franke wrote: > Takashi Yano via Cygwin wrote: > > On Mon, 24 Feb 2025 11:29:59 +0100 > > Christian Franke wrote: > >> Found with 'stress-ng --cpu-sched 1': > >> > >> Testcase (attached): > >> > >> $ uname -r > >> 3.6.0-0.387.g8cebbb2b42bf.x86_64 > >> > >