From: Craig Ruff <cruff@ucar.edu>
To: Richard Guenther <richard.guenther@student.uni-tuebingen.de>
Cc: Sane_Purushottam@emc.com, linux-kernel@vger.kernel.org
Subject: Re: fork and pthreads
Date: Fri, 16 Mar 2001 11:03:14 -0700 [thread overview]
Message-ID: <20010316110314.A24149@bells.scd.ucar.edu> (raw)
In-Reply-To: <93F527C91A6ED411AFE10050040665D0560664@corpusmx1.us.dg.com> <Pine.LNX.4.30.0103161850040.517-100000@fs1.dekanat.physik.uni-tuebingen.de>
In-Reply-To: <Pine.LNX.4.30.0103161850040.517-100000@fs1.dekanat.physik.uni-tuebingen.de>; from richard.guenther@student.uni-tuebingen.de on Fri, Mar 16, 2001 at 06:52:26PM +0100
On Fri, Mar 16, 2001 at 06:52:26PM +0100, Richard Guenther wrote:
> Well, using pthreads and forking in them seems to trigger libc
> bugs (read: SIGSEGvs) here under certain conditions (happens,
> after I introduced signal handlers and using pthread_sigmask,
> I think), so hangs should be definitely possible, too...
You must pretty much avoid using signal handlers with pthreads.
In stead, you need to carefully setup things such that most signals
are blocked in most threads and a single thread (or selected set
of threads) does a sigwait for signals of interest. Most good
pthreads books talk about this issue, as does the DCE documentation.
next prev parent reply other threads:[~2001-03-16 18:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-16 16:34 fork and pthreads Sane_Purushottam
2001-03-16 17:23 ` Doug McNaught
2001-03-16 17:52 ` Richard Guenther
2001-03-16 18:03 ` Craig Ruff [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-03-16 18:09 Sane, Purushottam
2001-03-16 23:11 ` Laramie Leavitt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010316110314.A24149@bells.scd.ucar.edu \
--to=cruff@ucar.edu \
--cc=Sane_Purushottam@emc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=richard.guenther@student.uni-tuebingen.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.