From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-475366-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 20557 invoked by alias); 29 Jan 2015 09:37:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Received: (qmail 20441 invoked by uid 48); 29 Jan 2015 09:36:59 -0000
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
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-61798-4-oEcRM0sqyh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61798-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61798-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-01/txt/msg03360.txt.bz2

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.