https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92305
--- Comment #5 from Tobias Burnus <burnus at gcc dot gnu.org> --- (In reply to seurer from comment #3) > Is there an easy way I can catch any of them that fire? Now fixed by using unique numbers in libgomp/testsuite. But replacing 'stop' by 'error stop' is one option - the exit code and output remains, but additionally a backtrace is shown. (Missed that option before; this just came into my mind right now.)
