bug#14569: 24.3.50; bootstrap fails on Cygwin

Paul Eggert eggert@cs.ucla.edu
Sat Jun 15 06:01:00 GMT 2013

On 06/14/2013 11:03 AM, Christopher Faylor wrote:

> You pointed to an archived mail messages which implies that was fixed
> more than a year ago.  What makes you think it is still a problem?

The message I pointed to <http://cygwin.com/ml/cygwin/2012-05/msg00472.html>
says this:

  > Testcase signal/kill:
  > Signals may or may not reach the correct thread with 1.7.12-1 and newer.

  Confirmed.  I think the reason is that we only have a single event to
  signal that a POSIX signal arrived instead of a per-thread event, but
  I'm not sure.  This is cgf's domain so I leave it at that for now.

I interpreted this to mean "the existence of the bug is confirmed,
here's why the bug occurs, and I'll let cgf deal with it".
I didn't see any followup message where cgf (is that you?)
dealt with it.  My apologies if I misinterpreted the email.

Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

More information about the Cygwin mailing list