[Autogenerated] As we've seen the S C H mechanism.
Is there, to handle low level exceptions generated directly by the processor.
The numbers might not be the same as we've seen.
So the number is zero, for example,
indicating divide by zero from the processor's perspective.
Is then translated by Windows to something else.
A different number, but still the original exception.
Is raised by the processor.
However,
if you've done any development with high level languages
such as C++ cs sharp or Java You're probably familiar with
the drive cache mechanism.
That allows us to catch exceptions raised by these languages or
the capabilities provided by these languages.
And the question, is is S C H connected up in some way.
To these kinds of exceptions or not.
And the answer, is that In general,
it depends on the implementation but on Windows for most cases,
it, is connected, and the idea here,
is that C++ .NET and Java use S C H internally by using a number,
that is available because the exception value the number itself,
is a 32-bit value than many of those numbers.
Of course, are available.
They just peak a certain number,
that they understand and then What happens there?
Is that They have a try accept handler of their own.
The particular run time like the C L R in .NET or the G V M in Java or the C++
runtime In case of C++ and when such except exception occurs.
Then they can get more details because every time you raise an
exception by calling the raise exception,
Windows API For example,
you can also supply a data structure called the exception record.
That can contain essentially any other information.
That makes sense for that exception, and the appropriate run time.
In this case, is the one that knows how to interpret that information,
to actually handle that correctly because in the high level languages,
the exceptions, are objects, they're not just simple numbers.
Their objects catch except an object type rather than some kind of number.
So, these object behind the scenes.
Is hiding behind these exception record,
data structure, that is used behind the scenes.
In the throw instructions,
that are provided by these kinds of high level languages.
One other note, is about C++ C++ doesn't have a Finally,
keyword just like um is available in cs sharp or Java for instance.
However, C++ does have a Destructor,
which means that It can make sure that things,
are running or executing in known locations at known times.
In fact,
the idiom using C++ to make finally kind of work without having a finally,
keyword, is known as the resources acquisition,
es initialization, ID or right, and I'll show you an example of that as well.
Let's start by looking at what these exceptions
look like at least to some extent.
In the win debug debugger