public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/30498] Support traceback (backtrace) on errors
Date: Thu, 18 Jan 2007 18:00:00 -0000	[thread overview]
Message-ID: <20070118175949.7378.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30498-13404@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from fxcoudert at gcc dot gnu dot org  2007-01-18 17:59 -------
(In reply to comment #0)
> "It was mentionned on IRC tonight that Daniel Berlin has a library that
> extracts line and file information from DWARF2 info. It's internal to Google, but he
> said he'll see if he can get it released. We'll have to get back to him in some
> time..."

I since spoke to him again, and we'd better go ahead with our current plan.


-- 

fxcoudert at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2007-01-18 17:59:49
               date|                            |


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


  reply	other threads:[~2007-01-18 18:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-18 12:46 [Bug libfortran/30498] New: " burnus at gcc dot gnu dot org
2007-01-18 18:00 ` fxcoudert at gcc dot gnu dot org [this message]
2007-02-07  9:08 ` [Bug libfortran/30498] " fxcoudert at gcc dot gnu dot org
2007-02-07  9:47 ` burnus at gcc dot gnu dot org
2007-02-08 20:30 ` patchapp at dberlin dot org
2007-02-09  7:44 ` P dot Schaffnit at access dot rwth-aachen dot de
2007-02-09  8:16 ` fxcoudert at gcc dot gnu dot org
2007-02-09  8:25 ` P dot Schaffnit at access dot rwth-aachen dot de
2007-02-09  9:56 ` burnus at gcc dot gnu dot org
2007-02-09 10:05 ` P dot Schaffnit at access dot rwth-aachen dot de
2007-02-09 13:25 ` P dot Schaffnit at access dot rwth-aachen dot de
2007-02-21 11:59 ` P dot Schaffnit at access dot rwth-aachen dot de
2007-03-10 16:47 ` burnus at gcc dot gnu dot org
2007-03-14 22:12 ` fxcoudert at gcc dot gnu dot org
2007-03-15 12:57 ` fxcoudert at gcc dot gnu dot org
2007-05-14  9:06 ` P dot Schaffnit at access dot rwth-aachen dot de

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=20070118175949.7378.qmail@sourceware.org \
    --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).