http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52594
--- Comment #7 from Janne Blomqvist <jb at gcc dot gnu.org> 2012-12-14 08:44:44 UTC --- (In reply to comment #6) > I was just about to file a bugreport that STOP 1 should yield a backtrace if > compiled with -fbacktrace.... that would really be useful to debug code that > just calls 'STOP 1' on some error condition (of course happening only with > 10000 MPI tasks, so no gdb as far as I can manage). I would be happy to have > -fbacktrace=STOP as a way to specify more explicitly when an error should > happen (generalizable to -fbacktrace=STOP,ALLOCATE,... ?) FWIW, you can get a backtrace by calling the ABORT intrinsic instead.
