[Autogenerated] Exceptions as opposed to interrupt,
are synchronous in nature,
which means that they occur because of certain process or
instruction where the process says Well,
I can't really move forward with that instruction.
For example, if you're dividing by zero or accessing memory,
which is not currently in ram,
the CP knows nothing about that and raises an exception called the page fault.
Same goes for break, mode which is another kind of exception.
So does an invalid instruction.
The case where the processor encounters an instruction,
it doesn't know how to interpret the exceptions we're talking about here.
Are low level exceptions generated by the processor itself.
It's not about high level exceptions you may be familiar with in
languages such as C++ C# or Java We'll see later in this module how
they relate to the underlying mechanism.
Windows provides for handling exceptions.
And that mechanism, is called structured exception handling or S C H.
This is the fundamental mechanism.
Windows provides for handling exceptions in user mode
and kernel mode and So it's possible.
To handle the exception, and If the exception,
is handled then the code will march on.
However, if this is not the case.
Then we'll get some kind of _____ if it's happening in
user mode that would be a process _____.
If the exception occurred in kernel mode that would be
a system _____ we've seen already.
That exceptions.
Are connected, to entries, in the inter, up dispatch table.
Let's take another look at that