From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27719 invoked by alias); 14 Dec 2012 08:44:58 -0000 Received: (qmail 27689 invoked by uid 48); 14 Dec 2012 08:44:44 -0000 From: "jb at gcc dot 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:44: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: jb at gcc dot gnu.org 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: In-Reply-To: References: 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: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2012-12/txt/msg01390.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52594 --- Comment #7 from Janne Blomqvist 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.