public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "olivier.grisel at ensta dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/58378] Protect libgomp against child process hanging after a Unix fork()
Date: Tue, 10 Sep 2013 10:51:00 -0000	[thread overview]
Message-ID: <bug-58378-4-zDMNOBgLFz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58378-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58378

--- Comment #4 from Olivier Grisel <olivier.grisel at ensta dot org> ---
Thanks for the explanation. Would you consider a solution that would preserve
the state of the parent process and would just reset the thread pool data on
the child?

Otherwise we will have to consider that the way fork() is used in Python's
multiprocessing module is really an abuse and that there is no way to safely
use both openmp-libraries and Python multiprocessing in the same program
safely.


  parent reply	other threads:[~2013-09-10 10:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-10  9:55 [Bug libgomp/58378] New: " olivier.grisel at ensta dot org
2013-09-10 10:00 ` [Bug libgomp/58378] " jakub at gcc dot gnu.org
2013-09-10 10:17 ` olivier.grisel at ensta dot org
2013-09-10 10:27 ` jakub at gcc dot gnu.org
2013-09-10 10:51 ` olivier.grisel at ensta dot org [this message]
2013-09-10 10:59 ` jakub at gcc dot gnu.org
2013-09-10 11:11 ` olivier.grisel at ensta dot org

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=bug-58378-4-zDMNOBgLFz@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).