This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libgomp/52303] libgomp leaves threads lying around that cause trouble if the program is later fork()'d
- From: "jakub at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sat, 18 Feb 2012 10:00:31 +0000
- Subject: [Bug libgomp/52303] libgomp leaves threads lying around that cause trouble if the program is later fork()'d
- Auto-submitted: auto-generated
- References: <bug-52303-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52303
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |jakub at gcc dot gnu.org
Resolution| |INVALID
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-02-18 10:00:31 UTC ---
That is not valid in POSIX, after fork from multi-threaded process (which is
any process that ever executed #pragma omp parallel too), POSIX lists just a
few functions that you may call after fork before you call _exit or exec*.
#pragma omp parallel is definitely not something you can do after fork from
multi-threaded programs.