お使いのブラウザが古くなっていますので、このウェブサイトのすべての機能が表示されない可能性があります。 お使いのブラウザの更新する方法をご覧ください。

OK

What is SEHException?

One way you get this exception is if unmanaged code does an OS RaiseException() or causes a fault.

If that exception is propagated up the stack to managed code, we will try to map it to a managed exception.

For example, STATUS_NO_MEMORY maps to OutOfMemoryException and STATUS_ACCESS_VIOLATION maps to NullReferenceException.

For all the exception codes that don’t have a predefined mapping, we wrap them up into SEHException.

In terms of pylon, when using C++ together with the Common Language Runtime (C++\CLI), any uncaught C++ exception will be converted into an .NET System.Runtime.InteropServices.SEHException when it reaches managed code (.NET code).

When programming with the pylon C++ API, the following exception handling is recommended:

try

{

//code using pylon

}

catch(const Pylon::GenericException& e)

{

//handle the exception

}

catch(const std::exception& e)

{

//handle the exception

}