This is the mail archive of the
mailing list for the Cygwin project.
Re: Sending SIGUSR1 to thread in nanosleep causes segfault
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Thu, 15 Jul 2010 10:54:49 -0400
- Subject: Re: Sending SIGUSR1 to thread in nanosleep causes segfault
- References: <AANLkTil1j8AMz_RV7_tEETMf2wioTrOr89miENO37fsw@mail.gmail.com>
- Reply-to: cygwin at cygwin dot 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.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple