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: Ulrich Drepper <drepper at redhat dot com>
To: Aidan Van Dyk <aidan at highrise dot ca>
Cc: Roland McGrath <roland at redhat dot com>, libc-alpha at sources dot redhat dot com
Date: Wed, 10 Sep 2003 12:40:49 -0700
Subject: Re: pthreads, fork+exec, and deadlocks
Organization: Red Hat, Inc.
References: <20030910153848.GM15256@biguy.highrise.ca> <200309101815.h8AIF7E10228@magilla.sf.frob.com> <20030910192039.GT15256@biguy.highrise.ca>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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.

- -- 
- --------------.                        ,-.            444 Castro Street
Ulrich Drepper \    ,-----------------'   \ Mountain View, CA 94041 USA
Red Hat         `--' drepper at redhat.com `---------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE/X35B2ijCOnn/RHQRApucAJ9EpbYrJWI3sRcIbOgYev4hEKQZvQCcDaKD
IFA/4esKePrWqKR2RKbgNSg=
=Px1X
-----END PGP SIGNATURE-----

Follow-Ups:
- Re: pthreads, fork+exec, and deadlocks
  - From: Aidan Van Dyk

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

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