public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <bug-46686-4-ZB71DAms4y@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46686-4@http.gcc.gnu.org/bugzilla/>

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!


  parent reply	other threads:[~2011-11-09 19:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-27 17:28 [Bug fortran/46686] New: Improve backtracing (unwinding) on MinGW burnus at gcc dot gnu.org
2011-05-06 21:33 ` [Bug fortran/46686] " fxcoudert at gcc dot gnu.org
2011-05-14 21:32 ` burnus at gcc dot gnu.org
2011-11-01 18:25 ` [Bug fortran/46686] Improve backtracing (unwinding) on non-glibc targets jb at gcc dot gnu.org
2011-11-09 16:20 ` jb at gcc dot gnu.org
2011-11-09 17:59 ` jb at gcc dot gnu.org
2011-11-09 18:10 ` burnus at gcc dot gnu.org
2011-11-09 19:30 ` burnus at gcc dot gnu.org
2011-11-09 19:49 ` jb at gcc dot gnu.org [this message]
2011-11-09 20:22 ` burnus at gcc dot gnu.org
2011-11-22 12:26 ` jb at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-46686-4-ZB71DAms4y@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).