X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=0.6 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org MIME-Version: 1.0 Date: Mon, 12 Jul 2010 11:56:47 -0500 Message-ID: Subject: pthread_mutex_lock doesn't interrupt From: James Cotton To: cygwin AT cygwin DOT com Content-Type: multipart/mixed; boundary=000e0cd56a226025bd048b33a3c6 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com --000e0cd56a226025bd048b33a3c6 Content-Type: text/plain; charset=ISO-8859-1 Hello, I've been trying to get the FreeRTOS Posix simulator to run on Cygwin and have run into a few bugs in the signal handling/pthread libraries and have isolated test cases I believe when pthread_mutex_lock receives an interrupt it should run it then resume trying to get a lock, the signal handler appears to never run (at least as inferred by no output. I tried running under cygwin gdb but get uniformative backtraces). Thanks, James --000e0cd56a226025bd048b33a3c6 Content-Type: application/octet-stream; name="test_case_4_mutex_lock.c" Content-Disposition: attachment; filename="test_case_4_mutex_lock.c" Content-Transfer-Encoding: base64 X-Attachment-Id: f_gbjk54te0 LyoqCiAqIHNtYWxsIGV0c3QgcHJvZ3JhbSB3aGV0aGVyIHNpZ25hbHMgYmV0 d2VlbiB0aHJlYWRzIHdvcmsgYXMgdGhleSBzaG91bGQKICovCgojaW5jbHVk ZSA8cHRocmVhZC5oPgojaW5jbHVkZSA8c2lnbmFsLmg+CgpzdGF0aWMgcHRo cmVhZF9tdXRleF90IE11dGV4ID0gUFRIUkVBRF9NVVRFWF9JTklUSUFMSVpF UjsKCi8qKgogKiBhY3R1YWwgdGVzdCBwcm9ncmFtCiAqLwoKdm9pZCBzaWdo YW5kbGVyKGludCBzaWcpIHsKCXdyaXRlKDIsIi4iLDEpOwoJd2hpbGUoMSk7 CglyZXR1cm47Cn0KCnZvaWQqIHRocmVhZHN0YXJ0KHZvaWQqIGFyZykgewoK CXdoaWxlICgxKSB7CgkJcHRocmVhZF9tdXRleF9sb2NrKCZNdXRleCk7Cgl9 Cn0KCmludCBtYWluKGNoYXIqKiBhcmdjLCBpbnQgYXJndikgewoKCXB0aHJl YWRfdCB0ZXN0dGhyZWFkMTsJCglzdHJ1Y3Qgc2lnYWN0aW9uIGFjdGlvbjsK CglhY3Rpb24uc2FfaGFuZGxlcj1zaWdoYW5kbGVyOwoJYWN0aW9uLnNhX2Zs YWdzPTA7CglzaWdmaWxsc2V0KCAmYWN0aW9uLnNhX21hc2sgKTsKCXNpZ2Fj dGlvbihTSUdVU1IxLCZhY3Rpb24sTlVMTCk7CgoJcHRocmVhZF9tdXRleF9s b2NrKCZNdXRleCk7CglwdGhyZWFkX2NyZWF0ZSgmdGVzdHRocmVhZDEsTlVM TCx0aHJlYWRzdGFydCxOVUxMKTsKCXdoaWxlICgxKSB7CgkJd3JpdGUoMiwi UyIsMSk7CgkJcHRocmVhZF9raWxsKHRlc3R0aHJlYWQxLFNJR1VTUjEpOwoJ fQp9Cg== --000e0cd56a226025bd048b33a3c6 Content-Type: text/plain; charset=us-ascii -- 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 --000e0cd56a226025bd048b33a3c6--