[Bug target/39530] [4.3/4.4/4.5 regression] runtime_error text not shown
--- 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
--- 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 throwing-exceptions-from-DLLs-even-with-a-static-libgcc patch or my port of it, including TDM-GCC releases *as well as* the nuwen.net release the initial reporter is using. -- 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
--- 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 dot org changed: What|Removed |Added CC||ktietz at gcc dot gnu dot ||org, dannysmith at gcc dot ||gnu dot org 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
--- 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
--- 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
--- 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 this, it is a mingw.org specific runtime failure. At least I could reproduce your reported bug also with 3.4.4 gcc. I verified this issue also with mingw-w64 32-bit runtime and couldn't reproduce it for this runtime. So you should report this problem to mingw.org. -- ktietz at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||INVALID 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
--- 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? Hmm, for w64 target runtime I get the result: $ ./tst.exe terminate called after throwing an instance of 'std::runtime_error' what(): ouch This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. This looks fine to me, isn't it? -- 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
--- 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. Well, as far as I verified this, it is a mingw.org specific runtime failure. At least I could reproduce your reported bug also with 3.4.4 gcc. I verified this issue also with mingw-w64 32-bit runtime and couldn't reproduce it for this runtime. So you should report this problem to mingw.org. Thanks https://sourceforge.net/tracker/?func=detailaid=2724976group_id=2435atid=102435 -- 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
--- 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 gcc-4.4.0, built from FSF sources, I get This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. terminate called after throwing an instance of 'std::runtime_error' what(): ouch With gcc-4.3.3, built from FSF sources, I get This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. terminate called after throwing an instance of 'std::runtime_error' what(): ouch I have not tested 4.3.3-dw2-tdm-1 which you report as the faulty build. Contrary to Kai Tietz assumption, it has nothing to do with mingw.org. Neither does it have anything to do with FSF gcc. Please report your bug to tdm -- 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
-- 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 |runtime_error text not shown Target Milestone|--- |4.3.4 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39530
