X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Thu, 15 Jul 2010 10:54:49 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Sending SIGUSR1 to thread in nanosleep causes segfault Message-ID: <20100715145449.GA25644@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Mon, Jul 12, 2010 at 11:36:04AM -0500, James Cotton wrote: >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 > >Essentially sending a SIGUSR1 to a pthread causes a segfault if that >thread is in sleep/nanosleep/select. This behavior continues if you >comment out the printing behavior. > >I believe at least nanosleep is meant to return when it receives a >signal so this seems like a bug. Well, yes. A SIGSEGV in cygwin code is always a bug. I'm investigating. I see how it happens but not why yet. cgf -- 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