public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "djh at emss dot co dot za" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/33903] Backtrace info in std::exception
Date: Fri, 02 Nov 2007 06:08:00 -0000	[thread overview]
Message-ID: <20071102060800.8885.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33903-15268@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from djh at emss dot co dot za  2007-11-02 06:08 -------
I am using debugger. After the exception is thrown, the program asserts.  So I
get a backtrace to the system fatal call, having no idea where the exception
was thrown.

I dont know about you guys but I find the .net/java exceptions with
backtraces built in to be a lot more useful.  Sure you can place a
breakpoint in the constructor of an exception but it has to be done and
can be very annoying in complicated debug sessions.  Especially since
GDB is not the fastest animal around and is being used used on larger
and larger projects (which take a _long_ time to load in gdb).


-- 


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


  parent reply	other threads:[~2007-11-02  6:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-26  7:11 [Bug libstdc++/33903] New: " djh at emss dot co dot za
2007-10-26  8:37 ` [Bug libstdc++/33903] " djh at emss dot co dot za
2007-10-26 10:22 ` pinskia at gcc dot gnu dot org
2007-11-02  6:08 ` djh at emss dot co dot za [this message]
2007-11-02  6:28 ` pinskia at gcc dot gnu dot org
2007-11-02  6:55 ` djh at emss dot co dot za
2007-11-05 15:44 ` pluto at agmk dot net
2007-12-02 22:27 ` pinskia at gcc dot gnu dot 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=20071102060800.8885.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).