From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30135 invoked by alias); 18 Nov 2011 13:45:47 -0000 Received: (qmail 30123 invoked by uid 22791); 18 Nov 2011 13:45:46 -0000 X-SWARE-Spam-Status: No, hits=-2.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,TW_BG X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 18 Nov 2011 13:45:33 +0000 From: "burnus at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/51197] [4.7 Regression] Backtrace information less useful Date: Fri, 18 Nov 2011 14:09: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: burnus at gcc dot gnu.org X-Bugzilla-Status: WAITING X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Status Last reconfirmed Ever Confirmed 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: 2011-11/txt/msg01887.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51197 Tobias Burnus changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |WAITING Last reconfirmed| |2011-11-18 Ever Confirmed|0 |1 --- Comment #4 from Tobias Burnus 2011-11-18 13:44:38 UTC --- (In reply to comment #2) > So it would be nice to actually write the SIG* information also > to stderr. (In reply to comment #3) > So to get back to the stdout/stderr issue, in 4.7 the last line of the output > is not printed by libgfortran but rather by the OS (libc?) default signal > handler for that signal (just like happens with -fno-backtrace). So libgfortran > has no say in where it goes. Harald, does this solve the issue? Or do you think that gfortran should replace the standard handler?