This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libfortran/36044] user-requested backtrace
- From: "burnus at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 28 Apr 2008 16:41:56 -0000
- Subject: [Bug libfortran/36044] user-requested backtrace
- References: <bug-36044-14773@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #3 from burnus at gcc dot gnu dot org 2008-04-28 16:41 -------
> > I think compiling with -fbacktrace and calling the STOP intrinsic should
> > emit a backtrace.
I think it should not. For abort(), I think a backtrace is ok, but for STOP
there should be no backtrace. Using stop is a quite normal way to stop a
program because a condition has not be met, e.g
stop 'Could not file "inp"'
If one finds afterwards dozens of lines of backtrace the actual message is no
longer visible. In my opinion, ifort shows too often a backtrace.
> I don't think it does.
Try abort(). (Though I do not recall whether it works, I think it does.)
> Anyway I'm looking for a solution that keeps the
> program running after the backtrace.
This can be sometimes indeed be handy, though I have never used it.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36044