Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
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 <cgf AT redhat DOT com>
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:	<OF732AE25C DOT 6B9A8CCC-ONC1256B68 DOT 0034E719 AT icos DOT be>
Mime-Version:	1.0
In-Reply-To:	<OF732AE25C.6B9A8CCC-ONC1256B68.0034E719@icos.be>
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/

- Raw text -