From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-373514-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 7550 invoked by alias); 9 Nov 2011 19:39:56 -0000
Received: (qmail 7480 invoked by uid 22791); 9 Nov 2011 19:39:55 -0000
X-SWARE-Spam-Status: No, hits=-2.9 required=5.0	tests=ALL_TRUSTED,AWL,BAYES_00
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; Wed, 09 Nov 2011 19:39:42 +0000
From: "jb at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/46686] Improve backtracing (unwinding) on non-glibc targets
Date: Wed, 09 Nov 2011 19:49: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: jb at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jb at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields:
Message-ID: <bug-46686-4-ZB71DAms4y@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-46686-4@http.gcc.gnu.org/bugzilla/>
References: <bug-46686-4@http.gcc.gnu.org/bugzilla/>
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: <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: 2011-11/txt/msg01010.txt.bz2

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

--- Comment #8 from Janne Blomqvist <jb at gcc dot gnu.org> 2011-11-09 19:38:49 UTC ---
(In reply to comment #7)
> (In reply to comment #6)
> > TODO: For Windows, one should be able to make use of SymFromAddr +
> > SymGetLineFromAddr64 + IMAGEHLP_LINE64 to obtain the symbol name
> 
> Kai points out that those only work with PDB and not with DWARF.
> 
> Though, it seems as if addr2line exists also for Windows. Kai thinks that is
> might/should work if one replaces for MINGW the path separator by ";" in
> libgfortran/runtime/main.c's find_addr2line. One probably needs to allow '\\'
> besides '/' under MinGW.

I thought that fork, exec, and pipe, which are necessary for starting and
interacting with the addr2line process are not supported on mingw? But, if it
works, great!