From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-250776-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 31712 invoked by alias); 25 Apr 2008 12:20:03 -0000
Received: (qmail 31529 invoked by uid 48); 25 Apr 2008 12:19:20 -0000
Date: Fri, 25 Apr 2008 12:20:00 -0000
Subject: [Bug libfortran/36044]  New: user-requested backtrace
X-Bugzilla-Reason: CC
Message-ID: <bug-36044-14773@http.gcc.gnu.org/bugzilla/>
Reply-To: gcc-bugzilla@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org
From: "jaydub66 at gmail dot com" <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: 2008-04/txt/msg01807.txt.bz2

It would be nice to have an intrinsic function to generate a user-requested
backtrace, like ifort's TRACEBACKQQ. Of course this would be a non-standard
extension, but a useful one which many other compilers also provide.

There has already been some discussion on this in PR30498, with suggested
workarounds like producing an FPE with "1.0/0.0" or calling 'kill' via
ISO_C_BINDING to generate a backtrace. But these of course terminate the
program.

For debugging purposes it can be helpful to generate a backtrace at some point
while keeping the program running, which is what e.g. TRACEBACKQQ does.


-- 
           Summary: user-requested backtrace
           Product: gcc
           Version: 4.4.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libfortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: jaydub66 at gmail dot com


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