This is the mail archive of the libc-alpha@sources.redhat.com mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: pthreads, fork+exec, and deadlocks

From: Aidan Van Dyk <aidan at highrise dot ca>
To: Ulrich Drepper <drepper at redhat dot com>
Cc: Roland McGrath <roland at redhat dot com>, libc-alpha at sources dot redhat dot com
Date: Wed, 10 Sep 2003 15:58:43 -0400
Subject: Re: pthreads, fork+exec, and deadlocks
References: <20030910153848.GM15256@biguy.highrise.ca> <200309101815.h8AIF7E10228@magilla.sf.frob.com> <20030910192039.GT15256@biguy.highrise.ca> <3F5F7E41.6070301@redhat.com>

* Ulrich Drepper <drepper@redhat.com> [030910 15:41]:
> Aidan Van Dyk wrote:
> 
> > The particular problem I'm seeing is with syslog_lock.
> 
> The standard doesn't guarantee that any functions but exec works after
> fork in a multi-threaded program.

Fair enough.  I hadn't found that.

Digging finds mention of "async-signal-safe functions" in the POSIX docs
on opengroup.org.

Is there a list of these functions for POSIX/glibc anywhere?

Thanks,
a.

-- 
Aidan Van Dyk                                             Create like a god,
aidan@highrise.ca                                       command like a king,
http://www.highrise.ca/                                   work like a slave.

Follow-Ups:
- Re: pthreads, fork+exec, and deadlocks
  - From: Ulrich Drepper

References:
- pthreads, fork+exec, and deadlocks
  - From: Aidan Van Dyk
- Re: pthreads, fork+exec, and deadlocks
  - From: Roland McGrath
- Re: pthreads, fork+exec, and deadlocks
  - From: Aidan Van Dyk
- Re: pthreads, fork+exec, and deadlocks
  - From: Ulrich Drepper

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]