From owner-freebsd-threads@FreeBSD.ORG Sun Dec 19 18:00:48 2004 Return-Path: Delivered-To: freebsd-threads@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8DA2B16A4CE for ; Sun, 19 Dec 2004 18:00:48 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77B8E43D2D for ; Sun, 19 Dec 2004 18:00:48 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id iBJI0meD095138 for ; Sun, 19 Dec 2004 18:00:48 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id iBJI0mbd095137; Sun, 19 Dec 2004 18:00:48 GMT (envelope-from gnats) Date: Sun, 19 Dec 2004 18:00:48 GMT Message-Id: <200412191800.iBJI0mbd095137@freefall.freebsd.org> To: freebsd-threads@FreeBSD.org From: Daniel Eischen Subject: Re: threads/75273: FBSD 5.3 libpthread (KSE) bug X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Daniel Eischen List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Dec 2004 18:00:48 -0000 The following reply was made to PR threads/75273; it has been noted by GNATS. From: Daniel Eischen To: "Enoch W." Cc: freebsd-gnats-submit@freebsd.org Subject: Re: threads/75273: FBSD 5.3 libpthread (KSE) bug Date: Sun, 19 Dec 2004 12:54:54 -0500 (EST) On Sun, 19 Dec 2004, Enoch W. wrote: > >Description: > sigsuspend() bug > > Thread aborts at /usr/src/lib/libpthread/thread/thr_sigsuspend.c line 77 with "oldsigmask is not cleared" when the main thread tries to pthread_cancel() it. > > FreeBSD 4.x (libc_r) does not have this problem. > > >How-To-Repeat: > > >Fix: > The easy solution :-) remove: > THR_ASSERT(curthread->oldsigmask == NULL, "oldsigmask is not cleared"); Sample program to demonstrate the problem, please? This could be fixed in -current, but since I don't know how to repeat the problem, I can't test it.