[Bug c++/39530] New: [regression] runtime_error text not shown

[Bug c++/39530] New: [regression] runtime_error text not shown

[shadow2531 at gmail dot com]

#include <stdexcept>
using namespace std;

int main() {
    throw runtime_error("ouch");
}

// g++ -Wall -Wextra test.cc -o test -O3 -s
// g++ (GCC) 4.3.3-dw2-tdm-1 <http://nuwen.net/mingw.html>
// WinXP SP3
// CMD.exe

Result:
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

Expected:
"ouch" should be shown somewhere in there. It used to be in < 4.3.


-- 
           Summary: [regression] runtime_error text not shown
           Product: gcc
           Version: 4.3.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: shadow2531 at gmail dot com


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

[Bug c++/39530] [regression] runtime_error text not shown

[shadow2531 at gmail dot com]

------- Comment #1 from shadow2531 at gmail dot com  2009-03-23 18:49 -------
Created an attachment (id=17525)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17525&action=view)
.ii file


-- 


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]

-- 

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

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

[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 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

[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?
> 

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

[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

[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

[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 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

[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.
> > 
> 
> 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=detail&aid=2724976&group_id=2435&atid=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

[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 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

[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=detail&aid=2726299&group_id=200665&atid=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

[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 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