From owner-freebsd-current  Thu Oct  1 15:16:31 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA16172
          for freebsd-current-outgoing; Thu, 1 Oct 1998 15:16:31 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from coleridge.kublai.com (coleridge.kublai.com [207.96.1.116])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA16167
          for <current@freebsd.org>; Thu, 1 Oct 1998 15:16:29 -0700 (PDT)
          (envelope-from shmit@coleridge.kublai.com)
Received: (from shmit@localhost)
	by coleridge.kublai.com (8.9.1/8.9.1) id SAA01387;
	Thu, 1 Oct 1998 18:16:02 -0400 (EDT)
Message-ID: <19981001181601.C228@kublai.com>
Date: Thu, 1 Oct 1998 18:16:01 -0400
From: Brian Cully <shmit@kublai.com>
To: John Birrell <jb@cimlogic.com.au>
Cc: current@FreeBSD.ORG
Subject: Re: Threading man pages.
Reply-To: shmit@kublai.com
References: <19981001175036.B228@kublai.com> <199810012207.IAA10855@cimlogic.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <199810012207.IAA10855@cimlogic.com.au>; from John Birrell on Fri, Oct 02, 1998 at 08:07:41AM +1000
X-Sender: If your mailer pays attention to this, it's broken.
X-PGP-Info: finger shmit@kublai.com for my public key.
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Fri, Oct 02, 1998 at 08:07:41AM +1000, John Birrell wrote:
> That is/was specific to sigwait() and shouldn't be generalized to
> "signal handling" in general. FWIW, Daniel is one of just a few people
> who actively contribute to this stuff.

Well, sigsuspend() doesn't appear to work properly, either. But
I'll need to do some more testing to verify that.

That, and there appear to be problems with the way pthread_create
and fork() interact. After I fork(), I do a bunch of pthread_creates
and my application just hangs. If I don't fork() everything works
fine.  Plus, my application works just fine under Solaris 2.6. I'm
not convinced that it's not my problem, but the code path up to
that point is pretty simple, and I can't see what the problem is.

> > So I should go ahead and do some man page frobbing?
> 
> I'm not sure exactly what you're going to frob. Do you have a copy of
> the POSIX standard to refer to? Remember that POSIX makes a lot of things
> optional.

I was going to start with the man pages to the various signal
functions, because that's what I've been dealing with recently.

No, I don't have a copy of the POSIX standard, but I have the
source, which should tell me everything I need to know (except for
the parts that don't adhere to the standard, but I was more interested
in a FreeBSD threads doc, and not a POSIX threads doc, which can
be added by someone who does have the standard). :-)

-bjc

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message