On Wed, Jan 30, 2019 at 4:23 PM Corinna Vinschen
wrote:
> > > > Poking around further, I find that replacing the signal generation
> > > > code in the test program for all cases with :
> > > >
> > > > pthread_kill(pthread_self(),sigid)
> > > >
> > > > generates compliant signal delivery behavior
> A minimal test program is copied below and also available here:
> https://upc-bugs.lbl.gov/bugzilla/attachment.cgi?id=589
> It's worth noting POSIX 1003.1-2016 sec XRAT.B.2.4.1 (p.3577)
> specifically requires that any given signal should be delivered to
> exactly one thread. Also the spec for a
in), I see substantially
the same misbehaviors.
Thanks,
-Dan Bonachea
On Tue, Jan 22, 2019 at 6:16 AM E. Madison Bray wrote:
>
> On Sun, Jan 20, 2019 at 9:34 PM Dan Bonachea wrote:
> >
> > I'm writing to report some POSIX compliance problems with Cygwin
> > signal handli
the Cygwin lists I find some evidence that
tangentially similar problems with signals and multithreading have
been discussed before, but perhaps not adequately
isolated/demonstrated.
Is there any hope of this situation ever improving?
Thanks for your consideration.
-Dan Bonachea
Test pr
n mailing list archives, user guide, FAQ, and
Google and not found a suitable answer. I've tried the peflags utility
mentioned in the Cygwin user guide, but that doesn't seem capable of
doing what I need, even for a single executable (although ideally I
want to enforce a system-wide
On Wed, Mar 8, 2017 at 11:48 AM, Corinna Vinschen
wrote:
>
> Thanks for the thorough analysis and especially the testcase!
>
> I applied a fix for this problem and uploaded new developer snapshots
> to https://cygwin.com/snapshots/
>
> Please give them a try.
Hi Corinna -
Thanks for the quick re
n
app-specific workaround not represented here), but I thought it
responsible to report the performance issue anyhow.
Thanks for your consideration.
-Dan Bonachea
========
// pthread-spawn.c test, by Dan Bonachea
7 matches
Mail list logo
