This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/51197] [4.7 Regression] Backtrace information less useful
- From: "burnus at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 18 Nov 2011 13:44:38 +0000
- Subject: [Bug fortran/51197] [4.7 Regression] Backtrace information less useful
- Auto-submitted: auto-generated
- References: <bug-51197-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51197
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2011-11-18
Ever Confirmed|0 |1
--- Comment #4 from Tobias Burnus <burnus at gcc dot gnu.org> 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?