Pra*_*tic 6 c++ exception language-lawyer terminate-handler
如果有以下程序的定义行为是什么?
#include <iostream>
#include <exception>
#include <cstdlib>
void i_throw()
{
std::cout << "i_throw()" << std::endl;
// std::terminate() is noexcept so if the terminate handler throws...
// then the terminate handler is called...
// std::terminate is [[noreturn]] so don't return
try
{
throw 7;
}
catch(...)
{
std::cout << "caught exception, re-throw()-ing" << std::endl;
throw;
}
std::cout << "got here!" << std::endl;
std::abort();
}
int main()
{
std::set_terminate(i_throw);
throw;
std::terminate();
}
Run Code Online (Sandbox Code Playgroud)
使用gcc和clang我得到以下输出:
i_throw()
caught exception, re-throw()-ing
Aborted (core dumped)
Run Code Online (Sandbox Code Playgroud)
在前几条评论后编辑的示例.
(我不知道为什么我有两个throw;
和std::terminate();
.我不想改变这个例子所以只假装其中只有一个在那里.)
上述问题可以归结为理解以下两个代码片段的行为。
示例 1: 抛出且没有活动异常
int main()
{
try{
throw;
}catch(...){
std::cout<<"caught"<<endl; //we never reach here
}
return 0;
}
Run Code Online (Sandbox Code Playgroud)
如果运行上面的代码,它会崩溃,如下所示
terminate called without an active exception
Aborted (core dumped)
Run Code Online (Sandbox Code Playgroud)
示例 2:抛出活动异常
int main()
{
try{
throw 7;
}catch(...){
std::cout<<"caught"<<endl; //will be caught
}
return 0;
}
Run Code Online (Sandbox Code Playgroud)
运行它会给出可预测的输出
caught
Run Code Online (Sandbox Code Playgroud)
如果生成代码的程序集 ( g++ -S option
)。您会注意到以下 cxx_abi 调用 throw 与 throw 7
throw;
被转换为call __cxa_rethrow
和
throw 7;
被转换为call __cxa_throw
这是代码__cxa_throw
extern "C" void
__cxxabiv1::__cxa_throw (void *obj, std::type_info *tinfo,
void (_GLIBCXX_CDTOR_CALLABI *dest) (void *))
{
PROBE2 (throw, obj, tinfo);
__cxa_eh_globals *globals = __cxa_get_globals ();
globals->uncaughtExceptions += 1;
// code removed for brevity
//.......
// Below code throws an exception to be caught by caller
#ifdef _GLIBCXX_SJLJ_EXCEPTIONS
_Unwind_SjLj_RaiseException (&header->exc.unwindHeader);
#else
_Unwind_RaiseException (&header->exc.unwindHeader);
#endif
// Some sort of unwinding error. Note that terminate is a handler.
__cxa_begin_catch (&header->exc.unwindHeader);
std::terminate ();
}
Run Code Online (Sandbox Code Playgroud)
因此,在OP代码throw 7;
中将被相应的捕获catch(...)
并被重新抛出throw;
这是代码__cxa__rethrow
extern "C" void
__cxxabiv1::__cxa_rethrow ()
{
__cxa_eh_globals *globals = __cxa_get_globals ();
__cxa_exception *header = globals->caughtExceptions; // We are not re
globals->uncaughtExceptions += 1;
// Watch for luser rethrowing with no active exception.
if (header)
{
// Code removed for brevity
// .....
// Below code rethrows the exception
#ifdef _GLIBCXX_SJLJ_EXCEPTIONS
_Unwind_SjLj_Resume_or_Rethrow (&header->unwindHeader);
#else
#if defined(_LIBUNWIND_STD_ABI)
_Unwind_RaiseException (&header->unwindHeader);
#else
_Unwind_Resume_or_Rethrow (&header->unwindHeader);
#endif
#endif
}
std::terminate ();
}
Run Code Online (Sandbox Code Playgroud)
在这两种情况下,我们都可以看到std::terminate()
尚未从__cxx_*
. 在被上述 abi 抛出后,我们位于代码中的以下位置。
请参阅cxx_abi来终止代码。
void
__cxxabiv1::__terminate (std::terminate_handler handler) throw ()
{
__try
{
handler (); // Our handler has thrown an int exception
std::abort ();
}
__catch(...) // Exception is caught here and process is aborted.
{ std::abort (); }
}
void
std::terminate () throw()
{
__terminate (get_terminate ());
}
Run Code Online (Sandbox Code Playgroud)
概括
根据我的理解,从处理程序重新抛出异常会导致在__cxxabiv1::__terminate
. 它在哪里召唤abort()
。显然,std::terminate()
[from __cxa_rethrow]方法没有出现,这就是为什么控件从未到达 std::cout << "got here!" << std::endl;
无限递归
如果我们将 Terminate_handler 更改为以下内容,会发生什么:
void i_throw()
{
std::cout << "i_throw()" << std::endl;
throw;
std::cout << "got here!" << std::endl;
std::abort();
}
Run Code Online (Sandbox Code Playgroud)
为了理解这一点,我们可以看看__cxa_rethrow()
上面提到的。
由于没有抛出任何活动的异常,因此__cxa_rethrow()
最终会调用std::terminate()
,从而导致无限递归。
归档时间: |
|
查看次数: |
1629 次 |
最近记录: |