This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libstdc++/78015] pthread_cancel while some exception is pending results in std::terminate ()


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78015

Jason Merrill <jason at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2016-10-18
     Ever confirmed|0                           |1

--- Comment #3 from Jason Merrill <jason at gcc dot gnu.org> ---
The problem is that non-C++ exceptions like forced unwind have no exception
header, so we can't chain them onto caughtExceptions.  But it seems to me that
we ought to be able to wrap such an exception in a C++ exception to make it
more palatable to the C++ runtime: in __cxa_catch, we can allocate a C++
exception using the foreign exception as the object.  Anyone see a problem with
this strategy?

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]