如果你正在寻找特定于windows的解决方案，那么有结构化异常处理: https://learn.microsoft.com/en-us/cpp/cpp/try-except-statement

代码如下所示

__try
{
   // code here may throw or make access violation
}
__except( EXCEPTION_EXECUTE_HANDLER )
{
    // after exception code here, e.g. log the error
}

它不仅可以捕获c++异常，还可以捕获访问违规或其他系统异常。

Can you run your JNI-using Java application from a console window (launch it from a java command line) to see if there is any report of what may have been detected before the JVM was crashed. When running directly as a Java window application, you may be missing messages that would appear if you ran from a console window instead. Secondly, can you stub your JNI DLL implementation to show that methods in your DLL are being entered from JNI, you are returning properly, etc? Just in case the problem is with an incorrect use of one of the JNI-interface methods from the C++ code, have you verified that some simple JNI examples compile and work with your setup? I'm thinking in particular of using the JNI-interface methods for converting parameters to native C++ formats and turning function results into Java types. It is useful to stub those to make sure that the data conversions are working and you are not going haywire in the COM-like calls into the JNI interface. There are other things to check, but it is hard to suggest any without knowing more about what your native Java methods are and what the JNI implementation of them is trying to do. It is not clear that catching an exception from the C++ code level is related to your problem. (You can use the JNI interface to rethrow the exception as a Java one, but it is not clear from what you provide that this is going to help.)

(在c++中)以可移植的方式捕获所有异常是不可能的。这是因为在c++上下文中，有些异常并不是异常。这包括除以零误差等。可以通过破解来获得在这些错误发生时抛出异常的能力，但这并不容易做到，当然也不容易以一种可移植的方式得到正确的处理。

如果你想捕获所有的STL异常，你可以这样做

try { ... } catch( const std::exception &e) { ... }

这将允许您使用e.what()，它将返回一个const char*，它可以告诉您有关异常本身的更多信息。这是与Java构造最相似的构造。

如果有人愚蠢地抛出一个不继承std::exception的异常，这将对您没有帮助。

有人应该补充说，在c++代码中无法捕捉“崩溃”。它们不会抛出异常，而是做任何它们喜欢做的事情。当你看到一个程序因为空指针的解引用而崩溃时，它正在做未定义的行为。没有std::null_pointer_exception。试图捕捉异常在那里没有帮助。

只是为了以防万一，有人正在阅读这篇文章，并认为他可以得到程序崩溃的原因。应该使用像gdb这样的调试器。

简单来说，使用catch(…)。但是，请注意catch(…)是与throw结合使用的;基本上:

try{
    foo = new Foo;
    bar = new Bar;
}
catch(...)       // will catch all possible errors thrown. 
{ 
    delete foo;
    delete bar;
    throw;       // throw the same error again to be handled somewhere else
}

这是使用catch(…)的正确方法。

请注意

try{
// ...
} catch (...) {
// ...
}

仅捕获语言级异常，其他低级异常/错误，如访问违反和分割错误不会被捕获。