public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/61798] OpenMP exit code 155, profiling related?
Date: Thu, 29 Jan 2015 09:37:00 -0000	[thread overview]
Message-ID: <bug-61798-4-oEcRM0sqyh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61798-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61798

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Exit code 155 is indeed that the process has been killed by SIGPROF signal.
Without a testcase there is hard to say anything more on this, libgomp
certainly doesn't install a signal handler for this signal, nor generate it,
nor do anything else with it, so I bet you'd get exactly the same situation if
you just used pthread_create yourself instead of OpenMP.


  reply	other threads:[~2015-01-29  9:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-14 10:16 [Bug libgomp/61798] New: " kessler at iag dot uni-stuttgart.de
2015-01-29  9:37 ` jakub at gcc dot gnu.org [this message]
2015-01-29  9:41 ` [Bug libgomp/61798] " pinskia at gcc dot gnu.org
2015-01-29 14:43 ` kessler at iag dot uni-stuttgart.de
2021-12-29  7:41 ` pinskia at gcc dot gnu.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-61798-4-oEcRM0sqyh@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).