From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Cc: 14569@debbugs.gnu.org
Subject: bug#14569: 24.3.50; bootstrap fails on Cygwin
Date: Sun, 16 Jun 2013 13:51:33 -0400 [thread overview]
Message-ID: <51BDFB25.8080101__17975.6633508534$1371405194$gmane$org@cornell.edu> (raw)
In-Reply-To: <20130616150141.GB3622@ednor.casa.cgf.cx>
On 6/16/2013 11:01 AM, Christopher Faylor wrote:
> On Sun, Jun 16, 2013 at 09:11:21AM -0400, Ken Brown wrote:
>> [Adding the bug address back to the CC so that this gets archived.]
>>
>> On 6/15/2013 9:54 AM, Angelo Graziosi wrote:
>>> Christopher Faylor wrote
>>>>> 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.
>>>>
>>>> Oops. I didn't read Corinna's message as thoroughly as I should have.
>>>> Sorry.
>>>>
>>>> That particular issue was supposed to have been fixed in Cygwin 1.7.17,
>>>> released in October 2012.
>>>
>>> Out of curiosity, I tried the test cases I found in that thread, more
>>> precisely here:
>>>
>>> http://cygwin.com/ml/cygwin/2012-05/msg00434.html
>>>
>>>
>>> and the results are:
>>>
>>> $ gcc otto_test1.c -o otto_test1
>>> $ ./otto_test1
>>> Testing deferred pthread_cancel()
>>>
>>> Thread 0 starting (0x200102c0)
>>> Thread 1 starting (0x20010360)
>>> Thread 2 starting (0x20010400)
>>>
>>> Cancelling thread 2 (0x20010400)
>>> Thread 2 exiting (0x20010400)
>>> Cancelling thread 1 (0x20010360)
>>> Thread 1 exiting (0x20010360)
>>> Cancelling thread 0 (0x200102c0)
>>> Thread 0 exiting (0x200102c0)
>>>
>>> Thread 0 is gone (0x200102c0)
>>> Thread 1 is gone (0x20010360)
>>> Thread 2 is gone (0x20010400)
>>>
>>> $ gcc otto_test2.c -o otto_test2
>>> $ ./otto_test2
>>> Testing asynchronous pthread_cancel()
>>>
>>> Thread 0 starting (0x200102c0)
>>> Changing canceltype from 0 to 1
>>> Thread 1 starting (0x20010360)
>>> Changing canceltype from 0 to 1
>>> Thread 2 starting (0x20010400)
>>> Changing canceltype from 0 to 1
>>>
>>> Cancelling thread 2 (0x20010400)
>>> Thread 2 exiting (0x20010400)
>>> Cancelling thread 1 (0x20010360)
>>> Thread 1 exiting (0x20010360)
>>> Cancelling thread 0 (0x200102c0)
>>> Thread 0 exiting (0x200102c0)
>>>
>>> Thread 0 is gone (0x200102c0)
>>> Thread 1 is gone (0x20010360)
>>> Thread 2 is gone (0x20010400)
>>>
>>> $ gcc otto_test3.c -o otto_test3
>>> $ ./otto_test3
>>> Testing pthread_kill()
>>>
>>> Thread 0 starting (0x200102c0)
>>> Thread 1 starting (0x20010360)
>>> Thread 2 starting (0x20010400)
>>>
>>> Sending SIGUSR1 to thread 2 (0x20010400)
>>> Thread 2 executes signal handler (0x20010400)
>>> Thread 2 encountered an error: Interrupted system call (0x20010400)
>>> Sending SIGUSR1 to thread 1 (0x20010360)
>>> Thread 1 executes signal handler (0x20010360)
>>> Thread 1 encountered an error: Interrupted system call (0x20010360)
>>> Sending SIGUSR1 to thread 0 (0x200102c0)
>>> Thread 0 executes signal handler (0x200102c0)
>>> Thread 0 encountered an error: Interrupted system call (0x200102c0)
>>>
>>> Are the errors in the last test case to be expected under the 20130612
>>> snapshot (CYGWIN_NT-5.1, 1.7.21s 20130612 21:06:59, i686 Cygwin)?
>>
>> I can replicate this on my system, consistently. There's clearly a
>> problem, but it's not the same as in the original Cygwin bug report. In
>> the present case, the signal is received by the right thread, but
>> something goes wrong afterwards.
>
> Try it on Linux. I don't see any difference. "An error" in this case
> seems to be the script working as designed.
>
> % man sem_wait
>
> SEM_WAIT(3) Linux Programmer's Manual SEM_WAIT(3)
>
>
>
> NAME
> sem_wait, sem_timedwait, sem_trywait - lock a semaphore
>
> ...
>
> ERRORS
> EINTR The call was interrupted by a signal handler; see signal(7).
Yeah, I missed that. Sorry for the noise.
Ken
next prev parent reply other threads:[~2013-06-16 17:51 UTC|newest]
Thread overview: 116+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-15 13:54 bug#14569: 24.3.50; bootstrap fails on Cygwin Angelo Graziosi
2013-06-16 13:11 ` Ken Brown
[not found] ` <51BDB979.3040508@cornell.edu>
[not found] ` <20130616150141.GB3622@ednor.casa.cgf.cx>
2013-06-16 17:51 ` Ken Brown [this message]
[not found] ` <51BDFB25.8080101@cornell.edu>
2013-06-16 18:20 ` Ken Brown
2013-06-22 20:49 ` Angelo Graziosi
2013-06-23 19:49 ` Angelo Graziosi
2013-06-23 20:47 ` Angelo Graziosi
2013-06-24 2:43 ` Eli Zaretskii
2013-06-24 0:34 ` Paul Eggert
2013-06-24 11:02 ` Ken Brown
2013-06-24 14:34 ` Paul Eggert
2013-06-24 15:51 ` Ken Brown
2013-06-24 16:55 ` Paul Eggert
2013-06-24 17:16 ` Ken Brown
2013-06-24 17:50 ` Angelo Graziosi
2013-06-24 21:05 ` Paul Eggert
2013-06-24 23:50 ` Angelo Graziosi
2013-06-25 13:34 ` Ken Brown
2013-06-25 13:55 ` Ken Brown
2013-06-25 14:51 ` Paul Eggert
2013-06-25 15:51 ` Ken Brown
2013-06-25 16:18 ` Paul Eggert
2013-06-27 14:56 ` Paul Eggert
2013-06-27 16:44 ` Angelo Graziosi
2013-06-27 16:54 ` Angelo Graziosi
2013-06-28 5:16 ` Paul Eggert
2013-06-27 19:32 ` Ken Brown
2013-06-28 12:20 ` Ken Brown
2013-06-28 14:50 ` Paul Eggert
2013-06-28 15:29 ` Ken Brown
2013-06-28 16:22 ` Angelo Graziosi
2013-06-28 21:40 ` Ken Brown
2013-07-01 11:21 ` Ken Brown
2013-07-01 12:28 ` Angelo Graziosi
2013-07-01 13:51 ` Ken Brown
2013-07-01 14:04 ` Ken Brown
2013-07-01 14:19 ` Paul Eggert
2013-07-01 16:16 ` Ken Brown
2013-07-01 17:31 ` Angelo Graziosi
2013-07-01 18:40 ` Ken Brown
2013-07-01 21:07 ` Paul Eggert
2013-07-01 21:47 ` Angelo Graziosi
2013-07-01 22:41 ` Ken Brown
2013-06-07 0:16 ` Katsumi Yamaoka
2013-06-10 13:54 ` Angelo Graziosi
2013-06-10 16:27 ` Jan Djärv
2013-06-10 18:56 ` Angelo Graziosi
2013-06-10 20:10 ` Paul Eggert
2013-06-10 21:15 ` Angelo Graziosi
2013-06-10 21:52 ` Paul Eggert
2013-06-10 22:06 ` Angelo Graziosi
2013-06-10 23:23 ` Angelo Graziosi
2013-06-11 15:13 ` Angelo Graziosi
2013-06-11 18:10 ` Paul Eggert
2013-06-11 20:13 ` Angelo Graziosi
2013-06-11 15:39 ` Jan Djärv
2013-06-11 16:58 ` Eli Zaretskii
2013-06-11 18:50 ` Paul Eggert
2013-06-11 19:26 ` Ken Brown
2013-06-11 19:53 ` Eli Zaretskii
2013-06-11 20:06 ` Ken Brown
2013-06-11 20:58 ` Jan Djärv
2013-06-11 20:59 ` Jan Djärv
2013-06-12 7:00 ` Jan Djärv
2013-06-12 18:33 ` Paul Eggert
2013-06-12 20:11 ` Angelo Graziosi
2013-06-13 7:08 ` Jan Djärv
2013-06-13 17:39 ` Paul Eggert
2013-06-14 9:11 ` Jan Djärv
2013-06-14 17:45 ` Paul Eggert
[not found] ` <51BB56CB.7030209@cs.ucla.edu>
2013-06-14 18:03 ` Christopher Faylor
2013-06-14 18:03 ` Christopher Faylor
2013-06-14 18:16 ` Eli Zaretskii
[not found] ` <20130614180359.GA5295@ednor.casa.cgf.cx>
2013-06-14 20:22 ` Ken Brown
[not found] ` <51BB7B82.4010204@cornell.edu>
2013-06-15 7:04 ` Eli Zaretskii
2013-06-15 9:54 ` Jan Djärv
2013-06-15 10:42 ` Eli Zaretskii
2013-06-15 12:47 ` Jan Djärv
2013-06-17 1:56 ` Ken Brown
2013-06-17 6:22 ` Jan Djärv
2013-06-17 15:06 ` Eli Zaretskii
2013-06-17 20:15 ` Ken Brown
2013-06-18 15:53 ` Eli Zaretskii
2013-06-19 20:24 ` Ken Brown
2013-06-20 2:45 ` Eli Zaretskii
2013-06-20 3:00 ` Ken Brown
2013-06-20 15:54 ` Eli Zaretskii
2013-06-22 15:13 ` Ken Brown
2013-06-22 19:04 ` Paul Eggert
2013-06-23 15:56 ` Ken Brown
2013-06-23 16:13 ` Eli Zaretskii
2013-06-23 18:22 ` Paul Eggert
2013-06-12 4:29 ` Katsumi Yamaoka
2013-07-02 2:19 ` Katsumi Yamaoka
2013-07-02 5:23 ` Katsumi Yamaoka
2013-07-02 11:22 ` Ken Brown
2013-07-02 13:57 ` Katsumi Yamaoka
2013-07-04 2:27 ` bug#14569: Emacs segfaulting on FreeBSD 9.1-RELEASE (amd64) during memory allocation wahjava.ml
2013-07-17 6:36 ` bug#14569: bug#14766: 24.3.50; sometimes "Memory exhausted" on Cygwin Katsumi Yamaoka
-- strict thread matches above, loose matches on Subject: below --
2013-07-02 13:57 Katsumi Yamaoka
2013-07-02 14:15 ` Angelo Graziosi
2013-07-03 2:31 ` Katsumi Yamaoka
2013-07-02 19:56 ` Ken Brown
2013-07-03 2:30 ` Katsumi Yamaoka
2013-07-03 3:24 ` Ken Brown
2013-07-03 4:54 ` Paul Eggert
2013-07-03 10:01 ` Katsumi Yamaoka
2013-07-03 10:57 ` Ken Brown
2013-07-03 11:48 ` Katsumi Yamaoka
2013-07-03 6:36 ` Michael Albinus
2013-07-03 10:01 ` Katsumi Yamaoka
[not found] <86d2qz3a7q.fsf@chateau.d.if>
2013-07-04 0:58 ` bug#14569: Emacs segfaulting on FreeBSD 9.1-RELEASE (amd64) during memory allocation Paul Eggert
2013-07-04 2:13 ` Ken Brown
[not found] ` <86txkbys94.fsf@chateau.d.if>
2013-07-04 6:23 ` Paul Eggert
2013-07-04 10:59 ` Ken Brown
2013-07-04 19:09 ` Ashish SHUKLA
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='51BDFB25.8080101__17975.6633508534$1371405194$gmane$org@cornell.edu' \
--to=kbrown@cornell.edu \
--cc=14569@debbugs.gnu.org \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).