This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/52594] no traceback expected for explicit fortran stop command combined with -fbacktrace
- From: "Joost.VandeVondele at mat dot ethz.ch" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 14 Dec 2012 08:47:14 +0000
- Subject: [Bug fortran/52594] no traceback expected for explicit fortran stop command combined with -fbacktrace
- Auto-submitted: auto-generated
- References: <bug-52594-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52594
--- Comment #8 from Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch> 2012-12-14 08:47:14 UTC ---
(In reply to comment #7)
> FWIW, you can get a backtrace by calling the ABORT intrinsic instead.
thanks... I'm using that now.
However, that requires changing a lot of places in the code unfortunately (and
abort is an extension, so we can't put it in the code 1-to-1).