public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "roland at gnu dot org" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs@sources.redhat.com
Subject: [Bug nptl/378] posix_spawn implementation, use vfork/execve rather than fork/execve for NPTL Linux.
Date: Mon, 13 Sep 2004 07:46:00 -0000 [thread overview]
Message-ID: <20040913074645.4078.qmail@sourceware.org> (raw)
In-Reply-To: <20040910004801.378.dennis@mds.rmit.edu.au>
------- Additional Comments From roland at gnu dot org 2004-09-13 07:46 -------
THe standard explicitly addresses the issue of pthread_atfork handlers being run
by posix_spawn, and specifies it to be implementation-defined. What that term
means is that the implementation is obliged to document what its behavior is in
that regard. Since glibc on GNU/Linux has heretofore always called
pthread_atfork handlers (because the code just calls `fork'), we have deemed
that "implementation-defined" for glibc on GNU/Linux here means that
pthread_atfork handlers do in fact get run. We may have failed to clearly
document this behavior, but it would be a disservice to users to have it change now.
--
http://sources.redhat.com/bugzilla/show_bug.cgi?id=378
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2004-09-13 7:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-10 0:48 [Bug nptl/378] New: " dennis at mds dot rmit dot edu dot au
2004-09-12 5:56 ` [Bug nptl/378] " drepper at redhat dot com
2004-09-12 18:06 ` drepper at redhat dot com
2004-09-12 22:54 ` roland at gnu dot org
2004-09-13 1:22 ` drepper at redhat dot com
2004-09-13 3:10 ` roland at gnu dot org
2004-09-13 4:18 ` dennis at mds dot rmit dot edu dot au
2004-09-13 6:35 ` jakub at redhat dot com
2004-09-13 7:46 ` roland at gnu dot org [this message]
2004-09-13 7:57 ` dennis at mds dot rmit dot edu dot au
2004-09-13 8:06 ` dennis at mds dot rmit dot edu dot au
2005-04-06 22:03 ` chris dot quenelle at sun dot com
[not found] <bug-378-131@http.sourceware.org/bugzilla/>
2014-06-13 10:43 ` fweimer at redhat dot com
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=20040913074645.4078.qmail@sourceware.org \
--to=sourceware-bugzilla@sources.redhat.com \
--cc=glibc-bugs@sources.redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).