From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1223 invoked by alias); 14 Dec 2012 07:59:46 -0000 Received: (qmail 1189 invoked by uid 48); 14 Dec 2012 07:59:32 -0000 From: "Joost.VandeVondele at mat dot ethz.ch" 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 07:59: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: CC 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/msg01388.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52594 Joost VandeVondele changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Joost.VandeVondele at mat | |dot ethz.ch --- Comment #6 from Joost VandeVondele 2012-12-14 07:59:30 UTC --- 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,... ?)