Namespaces
Variants
Views
Actions

Difference between revisions of "cpp/error/current exception"

From cppreference.com
< cpp‎ | error
(+)
 
m (fmt.)
 
(25 intermediate revisions by 12 users not shown)
Line 1: Line 1:
 
{{cpp/title|current_exception}}
 
{{cpp/title|current_exception}}
−
{{cpp/error/sidebar}}
+
{{cpp/error/navbar}}
−
 
+
{{ddcl|header=exception|since=c++11|
−
{{ddcl | header=exception | notes={{mark since c++11}} |
+
std::exception_ptr current_exception() noexcept;
−
std::exception_ptr current_exception()
+
 
}}
 
}}
  
−
If called during exception handling (typically, in a {{cpp|catch}} clause), captures the current exception object and creates an {{cpp|std::exception_ptr}} that holds a reference to that exception object, or to a copy of that exception object (it is implementation-defined if a copy is made)
+
If called during exception handling (typically, in a {{c/core|catch}} clause), captures the current exception object and creates an {{lc|std::exception_ptr}} that holds either a copy or a reference to that exception object (depending on the implementation). The referenced object remains valid at least as long as there is an {{tt|exception_ptr}} object that refers to it.
  
−
If the implementation of this function requires a call to {{cpp|new}} and the call fails, the returned pointer will hold a reference to an instance of {{cpp|std::bad_alloc}}
+
If the implementation of this function requires a call to {{c/core|new}} and the call fails, the returned pointer will hold a reference to an instance of {{lc|std::bad_alloc}}.
  
−
If the implementation of this function requires to copy the captured exception object and its copy constructor throws an exception, the returned pointer will hold a reference to the exception thrown. If the copy constructor of the thrown exception object also throws, the returned pointer may hold a reference to an instance of {{cpp|std::bad_exception}} to break the endless loop.
+
If the implementation of this function requires copying the captured exception object and its copy constructor throws an exception, the returned pointer will hold a reference to the exception thrown. If the copy constructor of the thrown exception object also throws, the returned pointer may hold a reference to an instance of {{lc|std::bad_exception}} to break the endless loop.
  
−
If the function is called when no exception is being handled, an empty {{cpp|std::exception_ptr}} is returned.
+
If the function is called when no exception is being handled, an empty {{lc|std::exception_ptr}} is returned.
 +
 
 +
This function can be called in a {{lc|std::terminate_handler}} to retrieve the exception which has provoked the invocation of {{lc|std::terminate}}.
  
 
===Parameters===
 
===Parameters===
Line 18: Line 19:
  
 
===Return value===
 
===Return value===
−
An instance of {{cpp|std::exception_ptr}} holding a reference to the exception object, or a copy of the exception object, or to an instance of {{cpp|std::bad_alloc}} or to an instance of {{cpp|std::bad_exception}}.
+
An instance of {{lc|std::exception_ptr}} holding a reference to the exception object, or a copy of the exception object, or to an instance of {{lc|std::bad_alloc}} or to an instance of {{lc|std::bad_exception}}.
  
−
===Exceptions===
+
===Notes===
−
{{noexcept}}
+
On the implementations that follow [https://itanium-cxx-abi.github.io/cxx-abi/abi.html Itanium C++ ABI] (GCC, Clang, etc), exceptions are allocated on the heap when thrown (except for {{lc|std::bad_alloc}} in some cases), and this function simply creates the smart pointer referencing the previously-allocated object, On MSVC, exceptions are allocated on stack when thrown, and this function performs the heap allocation and copies the exception object.
 +
 
 +
On Windows in managed CLR environments [https://learn.microsoft.com/en-us/cpp/dotnet/exceptions-in-cpp-cli], the implementation will store a {{lc|std::bad_exception}} when the current exception is a managed exception ([https://github.com/microsoft/STL/blob/65aab97a8e75e7ba409002e518ed799006dfb285/stl/src/excptptr.cpp#L367]). Note that {{c|catch(...)}} catches also managed exceptions:
 +
{{source|1=
 +
#include <exception>
 +
 
 +
int main()
 +
{
 +
    try
 +
    {
 +
        throw gcnew System::Exception("Managed exception");
 +
    }
 +
    catch (...)
 +
    {
 +
        std::exception_ptr ex = std::current_exception();
 +
        try
 +
        {
 +
            std::rethrow_exception(ex);
 +
        }
 +
        catch (std::bad_exception const &)
 +
        {
 +
            // This will be printed.
 +
            std::cout << "Bad exception" << std::endl;
 +
        }
 +
    }
 +
}
 +
}}
  
 
===Example===
 
===Example===
−
{{cpp/error/exception/example_exception_ptr}}
+
{{include|cpp/error/example_exception_ptr}}
  
 
===See also===
 
===See also===
−
{{dcl list begin}}
+
{{dsc begin}}
−
{{dcl list template | cpp/error/exception/dcl list exception_ptr}}
+
{{dsc inc|cpp/error/dsc exception_ptr}}
−
{{dcl list template | cpp/error/exception/dcl list rethrow_exception}}
+
{{dsc inc|cpp/error/dsc rethrow_exception}}
−
{{dcl list template | cpp/error/exception/dcl list make_exception_ptr}}
+
{{dsc inc|cpp/error/dsc make_exception_ptr}}
−
{{dcl list end}}
+
{{dsc inc|cpp/error/dsc uncaught_exception}}
 +
{{dsc end}}
 +
 
 +
{{langlinks|de|es|fr|it|ja|pt|ru|zh}}

Latest revision as of 09:47, 9 July 2024

 
C++
 
Diagnostics library
 
Defined in header <exception>
std::exception_ptr current_exception() noexcept;
 (since C++11)

If called during exception handling (typically, in a catch clause), captures the current exception object and creates an std::exception_ptr that holds either a copy or a reference to that exception object (depending on the implementation). The referenced object remains valid at least as long as there is an exception_ptr object that refers to it.

If the implementation of this function requires a call to new and the call fails, the returned pointer will hold a reference to an instance of std::bad_alloc.

If the implementation of this function requires copying the captured exception object and its copy constructor throws an exception, the returned pointer will hold a reference to the exception thrown. If the copy constructor of the thrown exception object also throws, the returned pointer may hold a reference to an instance of std::bad_exception to break the endless loop.

If the function is called when no exception is being handled, an empty std::exception_ptr is returned.

This function can be called in a std::terminate_handler to retrieve the exception which has provoked the invocation of std::terminate.

Contents

[edit] Parameters

(none)

[edit] Return value

An instance of std::exception_ptr holding a reference to the exception object, or a copy of the exception object, or to an instance of std::bad_alloc or to an instance of std::bad_exception.

[edit] Notes

On the implementations that follow Itanium C++ ABI (GCC, Clang, etc), exceptions are allocated on the heap when thrown (except for std::bad_alloc in some cases), and this function simply creates the smart pointer referencing the previously-allocated object, On MSVC, exceptions are allocated on stack when thrown, and this function performs the heap allocation and copies the exception object.

On Windows in managed CLR environments [1], the implementation will store a std::bad_exception when the current exception is a managed exception ([2]). Note that catch(...) catches also managed exceptions: 

#include <exception>
 
int main()
{
    try
    {
        throw gcnew System::Exception("Managed exception");
    }
    catch (...)
    {
        std::exception_ptr ex = std::current_exception();
        try
        {
            std::rethrow_exception(ex);
        }
        catch (std::bad_exception const &)
        {
            // This will be printed.
            std::cout << "Bad exception" << std::endl;
        }
    }
}

[edit] Example

[edit]
Run this code
#include <exception>
#include <iostream>
#include <stdexcept>
#include <string>
 
void handle_eptr(std::exception_ptr eptr) // passing by value is OK
{
    try
    {
        if (eptr)
            std::rethrow_exception(eptr);
    }
    catch(const std::exception& e)
    {
        std::cout << "Caught exception: '" << e.what() << "'\n";
    }
}
 
int main()
{
    std::exception_ptr eptr;
 
    try
    {
        [[maybe_unused]]
        char ch = std::string().at(1); // this generates a std::out_of_range
    }
    catch(...)
    {
        eptr = std::current_exception(); // capture
    }
 
    handle_eptr(eptr);
 
} // destructor for std::out_of_range called here, when the eptr is destructed

Possible output: 

Caught exception: 'basic_string::at: __n (which is 1) >= this->size() (which is 0)'

[edit] See also

(C++11)
 shared pointer type for handling exception objects
(typedef) [edit]
(C++11)
 throws the exception from an std::exception_ptr
(function) [edit]
(C++11)
 creates an std::exception_ptr from an exception object
(function template) [edit]
(removed in C++20*)(C++17)
 checks if exception handling is currently in progress
(function) [edit]
Retrieved from "https://en.cppreference.com/mwiki/index.php?title=cpp/error/current_exception&oldid=173422"