From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-209624-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 2385 invoked by alias); 7 Feb 2007 09:47:10 -0000
Received: (qmail 2343 invoked by uid 48); 7 Feb 2007 09:47:01 -0000
Date: Wed, 07 Feb 2007 09:47:00 -0000
Message-ID: <20070207094701.2342.qmail@sourceware.org>
X-Bugzilla-Reason: CC
References: <bug-30498-13404@http.gcc.gnu.org/bugzilla/>
Subject: [Bug libfortran/30498] Support traceback (backtrace) on errors
In-Reply-To: <bug-30498-13404@http.gcc.gnu.org/bugzilla/>
Reply-To: gcc-bugzilla@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2007-02/txt/msg00867.txt.bz2



------- Comment #3 from burnus at gcc dot gnu dot org  2007-02-07 09:47 -------
> Patch implementing the -fbacktrace option

I think one should add also some userhandler
  signal(SIGSEGV, my_segv_handler);
which calls show_backtrace and exits/coredumps then.

That way we calso get a backtrace for signalling arithmetic errors or for wrong
pointer accesses etc.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30498