--- Comment #6 from pinskia at gcc dot gnu dot org 2007-12-02 22:27 ---
Not really a good request as GCC support for this is hard and non standard.
You can do it yourself as shown below.
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Add
--- Comment #5 from pluto at agmk dot net 2007-11-05 15:44 ---
(In reply to comment #4)
> This is a possible solution. Not ideal though, because, then all exceptions
> will be trigger the breakpoint at __cxa_throw.
>
> If however, I put a breakpoint in the catch in question, then I kno
--- Comment #4 from djh at emss dot co dot za 2007-11-02 06:54 ---
This is a possible solution. Not ideal though, because, then all exceptions
will be trigger the breakpoint at __cxa_throw.
If however, I put a breakpoint in the catch in question, then I know I will get
the exception th
--- Comment #3 from pinskia at gcc dot gnu dot org 2007-11-02 06:27 ---
(In reply to comment #2)
> 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.
Since GCC follow
--- 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
--- Comment #1 from pinskia at gcc dot gnu dot org 2007-10-26 10:22 ---
I would use a debugger if you want the backtrace info.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33903
--
djh at emss dot co dot za changed:
What|Removed |Added
Severity|normal |enhancement
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33903
