Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Fri, 22 Feb 2002 11:08:45 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: minor bugs in pthread_setcancelstate and pthread_setcanceltype Message-ID: <20020222160845.GE15032@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23.1i On Fri, Feb 22, 2002 at 10:45:18AM +0100, dirk DOT derycke AT icos DOT be wrote: > >Hi all, > >for the functions (thread.cc): >int __pthread_setcancelstate (int state, int *oldstate) >int __pthread_setcanceltype (int type, int *oldtype) >can somebody add the checking whether the pointers oldstate and oldtype are >nill pointers? > >The Linux man page says that the previous state/type is not saved when the >pointer is zero. >Currently we get the annoying SIGSEGV crash when the old state/type is >written to address 0x0. How about trying a patch for this behavior? It sounds like it would be trivial and you would be helping out the pthreads developer. http://cygwin.com/contrib.html There is no need for an assignment in this case since the patch should be both obvious and trivial. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/