[Bug target/39530] [4.3/4.4/4.5 regression] runtime_error text not shown

2009-04-02 Thread shadow2531 at gmail dot com
--- Comment #9 from shadow2531 at gmail dot com 2009-04-02 07:24 --- Filed tdm bug: https://sourceforge.net/tracker/?func=detailaid=2726299group_id=200665atid=974439 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39530

[Bug target/39530] [4.3/4.4/4.5 regression] runtime_error text not shown

2009-04-02 Thread tdragon at tdragon dot net
--- Comment #10 from tdragon at tdragon dot net 2009-04-02 23:57 --- This is the exact same behavior as is present in the most recent MinGW stable release of GCC (3.4.5-20060117-3), and will be present in any release which uses Danny's

[Bug target/39530] [4.3/4.4/4.5 regression] runtime_error text not shown

2009-04-01 Thread jakub at gcc dot gnu dot org
--- Comment #2 from jakub at gcc dot gnu dot org 2009-04-01 09:00 --- __gnu_cxx::__verbose_terminate_handler hasn't been called then, doesn't the mingw runtime override __cxxabiv1::__terminate_handler or the unwinding on mingw not call std::terminate at all? -- jakub at gcc dot gnu

[Bug target/39530] [4.3/4.4/4.5 regression] runtime_error text not shown

2009-04-01 Thread jakub at gcc dot gnu dot org
--- Comment #4 from jakub at gcc dot gnu dot org 2009-04-01 09:24 --- Sure (assuming the weirdo message after it is M$ abort verbiage). The question is if the reporter sees it as well and if not, why. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39530

[Bug target/39530] [4.3/4.4/4.5 regression] runtime_error text not shown

2009-04-01 Thread shadow2531 at gmail dot com
--- Comment #5 from shadow2531 at gmail dot com 2009-04-01 09:30 --- (In reply to comment #3) terminate called after throwing an instance of 'std::runtime_error' what(): ouch Yes, this is the part that's missing for me. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39530

[Bug target/39530] [4.3/4.4/4.5 regression] runtime_error text not shown

2009-04-01 Thread ktietz at gcc dot gnu dot org
--- Comment #6 from ktietz at gcc dot gnu dot org 2009-04-01 10:44 --- (In reply to comment #5) (In reply to comment #3) terminate called after throwing an instance of 'std::runtime_error' what(): ouch Yes, this is the part that's missing for me. Well, as far as I verified

[Bug target/39530] [4.3/4.4/4.5 regression] runtime_error text not shown

2009-04-01 Thread ktietz at gcc dot gnu dot org
--- Comment #3 from ktietz at gcc dot gnu dot org 2009-04-01 09:18 --- (In reply to comment #2) __gnu_cxx::__verbose_terminate_handler hasn't been called then, doesn't the mingw runtime override __cxxabiv1::__terminate_handler or the unwinding on mingw not call std::terminate at all?

[Bug target/39530] [4.3/4.4/4.5 regression] runtime_error text not shown

2009-04-01 Thread shadow2531 at gmail dot com
--- Comment #7 from shadow2531 at gmail dot com 2009-04-01 12:15 --- (In reply to comment #6) (In reply to comment #5) (In reply to comment #3) terminate called after throwing an instance of 'std::runtime_error' what(): ouch Yes, this is the part that's missing for me.

[Bug target/39530] [4.3/4.4/4.5 regression] runtime_error text not shown

2009-04-01 Thread dannysmith at users dot sourceforge dot net
--- Comment #8 from dannysmith at users dot sourceforge dot net 2009-04-02 04:20 --- (In reply to comment #5) (In reply to comment #3) terminate called after throwing an instance of 'std::runtime_error' what(): ouch Yes, this is the part that's missing for me. With

[Bug target/39530] [4.3/4.4/4.5 regression] runtime_error text not shown

2009-03-31 Thread jsm28 at gcc dot gnu dot org
-- jsm28 at gcc dot gnu dot org changed: What|Removed |Added Summary|[regression] runtime_error |[4.3/4.4/4.5 regression] |text not shown