This is the mail archive of the fortran@gcc.gnu.org mailing list for the GNU Fortran project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [gfortran,patch, RFC] Allow coredump and backtrace on runtime error

From: Jerry DeLisle <jvdelisle at verizon dot net>
Cc: "fortran at gcc dot gnu dot org" <fortran at gcc dot gnu dot org>, gcc-patches <gcc-patches at gcc dot gnu dot org>
Date: Fri, 24 Nov 2006 09:58:17 -0800
Subject: Re: [gfortran,patch, RFC] Allow coredump and backtrace on runtime error
References: <19c433eb0611240855v68a78b1ftda3ef385932300e6@mail.gmail.com>

François-Xavier Coudert wrote:


 -- I made -fbacktrace the default behaviour, because it doesn't cost
a CPU cycle during execution. Do you think that makes the output too
verbose?

I don't think we need all the clutter. I think that if a user is knowledgeable and can use a backtrace, they can ask for it. For most errors it is not needed.

Great work.

Jerry

Follow-Ups:
- Re: [gfortran,patch, RFC] Allow coredump and backtrace on runtime error
  - From: Tobias Burnus

References:
- [gfortran,patch, RFC] Allow coredump and backtrace on runtime error
  - From: François-Xavier Coudert

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]