This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/33903] Backtrace info in std::exception
- From: "djh at emss dot co dot za" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 2 Nov 2007 06:08:00 -0000
- Subject: [Bug libstdc++/33903] Backtrace info in std::exception
- References: <bug-33903-15268@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- 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