[Bug libgomp/61798] New: OpenMP exit code 155, profiling related?

[kessler at iag dot uni-stuttgart.de]

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

            Bug ID: 61798
           Summary: OpenMP exit code 155, profiling related?
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libgomp
          Assignee: unassigned at gcc dot gnu.org
          Reporter: kessler at iag dot uni-stuttgart.de
                CC: jakub at gcc dot gnu.org

I have got an OpenMP program (written in C++) up and running. However, when
running my test suite of 43 cases for profiling (with -pg, it's CFD flow solver
running in batch mode), some (usually 2-3) cases fail with an exit code of 155
-after- full completion of my code (that is, after return 0; in main). This
only happens if several codes run in parallel on the same machine (this
capability of the test script is from before the OpenMP parallelisation
effort), and even then not always, and with varying cases, so I am quite
confident it is not primarily a bug in my code.
>From scanning the output I have seen a message from the shell, apparently
catching a SIGPROF, which seems reasonable as I have profiling enabled, but
probably should not propagate outside the executable. I have never seen this
problem with profiling in non-OpenMP mode.
Unfortunately I can not share my code, but I think it is not related to the
user code anyway, but perhaps some race condition in the interaction between
profiling and OpenMP at program exit?

Thanks for shedding some light on this bizarre situation.

Ciao,

    Manuel