From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-409783-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 28657 invoked by alias); 14 Dec 2012 08:47:28 -0000
Received: (qmail 28623 invoked by uid 48); 14 Dec 2012 08:47:16 -0000
From: "Joost.VandeVondele at mat dot ethz.ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/52594] no traceback expected for explicit fortran stop command combined with -fbacktrace
Date: Fri, 14 Dec 2012 08:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: Joost.VandeVondele at mat dot ethz.ch
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields:
Message-ID: <bug-52594-4-wY1VpwmKrr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-52594-4@http.gcc.gnu.org/bugzilla/>
References: <bug-52594-4@http.gcc.gnu.org/bugzilla/>
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2012-12/txt/msg01391.txt.bz2


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).