On Nov 2 23:54, John Carey wrote:
> > From: Corinna Vinschen [corinna-cyg...@cygwin.com]
> > Sent: Monday, November 02, 2015 9:58 AM
> > On Nov 2 15:18, Corinna Vinschen wrote:
> > > On Oct 29 16:16, John Carey wrote:
> > > > > From: Corinna Vinschen [corinna-cyg...@cygwin.com]
> > > > > Sent: Th
> From: Corinna Vinschen [corinna-cyg...@cygwin.com]
> Sent: Monday, November 02, 2015 9:58 AM
> On Nov 2 15:18, Corinna Vinschen wrote:
> > On Oct 29 16:16, John Carey wrote:
> > > > From: Corinna Vinschen [corinna-cyg...@cygwin.com]
> > > > Sent: Thursday, October 29, 2015 1:02 AM
> > > > On Oct
On Nov 2 15:18, Corinna Vinschen wrote:
> On Oct 29 16:16, John Carey wrote:
> > > From: Corinna Vinschen [corinna-cyg...@cygwin.com]
> > > Sent: Thursday, October 29, 2015 1:02 AM
> > > On Oct 28 10:14, Corinna Vinschen wrote:
> > ...
> > > > > Thanks; that was fast! I tried replacing cygwin1.dl
On Oct 29 16:16, John Carey wrote:
> > From: Corinna Vinschen [corinna-cyg...@cygwin.com]
> > Sent: Thursday, October 29, 2015 1:02 AM
> > On Oct 28 10:14, Corinna Vinschen wrote:
> ...
> > > > Thanks; that was fast! I tried replacing cygwin1.dll with
> > > > cygwin1-20151023.dll .
> > > >
> > >
> From: Corinna Vinschen [corinna-cyg...@cygwin.com]
> Sent: Thursday, October 29, 2015 1:02 AM
> On Oct 28 10:14, Corinna Vinschen wrote:
...
> > > Thanks; that was fast! I tried replacing cygwin1.dll with
> > > cygwin1-20151023.dll .
> > >
> > > The original test case now works. I checked some
On Oct 28 10:14, Corinna Vinschen wrote:
> On Oct 27 19:06, John Carey wrote:
> > Sorry for the delay.
> >
> > From: Corinna Vinschen [corinna-cyg...@cygwin.com]
> > Sent: Friday, October 23, 2015 5:55 AM
> > > > I've attached a test case that I *think* gets into the right spot, at
> > > > least f
On Oct 27 19:06, John Carey wrote:
> Sorry for the delay.
>
> From: Corinna Vinschen [corinna-cyg...@cygwin.com]
> Sent: Friday, October 23, 2015 5:55 AM
> > > I've attached a test case that I *think* gets into the right spot, at
> > > least for 64-bit Cygwin 2.0.4. That is, it hangs trying to re
Sorry for the delay.
From: Corinna Vinschen [corinna-cyg...@cygwin.com]
Sent: Friday, October 23, 2015 5:55 AM
> > I've attached a test case that I *think* gets into the right spot, at
> > least for 64-bit Cygwin 2.0.4. That is, it hangs trying to receive
> > the signal, instead of terminating.
John? Ping?
On Oct 23 14:55, Corinna Vinschen wrote:
> On Oct 22 02:08, John Carey wrote:
> > > From: Corinna Vinschen [corinna-cyg...@cygwin.com]
> > > Sent: Wednesday, October 21, 2015 4:48 AM
> > > Subject: Re: pthread_kill: signals remain pending af
On Oct 22 02:08, John Carey wrote:
> > From: Corinna Vinschen [corinna-cyg...@cygwin.com]
> > Sent: Wednesday, October 21, 2015 4:48 AM
> > Subject: Re: pthread_kill: signals remain pending after target thread exits
> ...
> > > On Sep 11 18:11, John Carey wrote:
>
> From: Corinna Vinschen [corinna-cyg...@cygwin.com]
> Sent: Wednesday, October 21, 2015 4:48 AM
> Subject: Re: pthread_kill: signals remain pending after target thread exits
...
> > On Sep 11 18:11, John Carey wrote:
> > There seems to be a problem with pthread_k
Hi John,
On Sep 11 18:11, John Carey wrote:
> There seems to be a problem with pthread_kill: a pending signal
> targeting a particular thread prevents other threads from receiving
> signals sharing the same signal number--even after the original target
> thread exits and is joined.
>
> To reprodu
There seems to be a problem with pthread_kill: a pending signal targeting a
particular thread prevents other threads from receiving signals sharing the
same signal number--even after the original target thread exits and is joined.
To reproduce the issue:
1. Block signal number S.
2. Create
13 matches
Mail list logo