Create a new “Handling Exceptions” post #292

Merged
merged 12 commits into from Mar 26, 2017

Conversation

2 participants
@phil-opp
Owner

phil-opp commented Mar 21, 2017

This post combines the previous exception handling posts “Catching Exceptions”, “Better Exception Messages” and “Returning from Exceptions” into a single post by using the x86-interrupt calling convention and the Idt type of the x86_64 crate.

blog/content/post/handling-exceptions.md
+### Faults, Aborts, and Traps
+The answer is that the stored instruction pointer only points to the causing instruction for _fault_ type exceptions, but not for _trap_ or _abort_ type exceptions. The difference between these types is the following:
+
+- **Faults** are exceptions that can be corrected so that the program can continiue as if nothing happened. An example is the [page fault], which can often be resolved by loading the accessed page from the disk into memory.

This comment has been minimized.

@bjorn3

bjorn3 Mar 21, 2017

*continue

This comment has been minimized.

@phil-opp

phil-opp Mar 22, 2017

Owner

Thanks!

@phil-opp

phil-opp Mar 22, 2017

Owner

Thanks!

@phil-opp phil-opp merged commit 1cc5f05 into master Mar 26, 2017

3 checks passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
continuous-integration/travis-ci/push The Travis CI build passed
Details
deploy/netlify Deploy preview ready!
Details

@phil-opp phil-opp deleted the handling-exceptions branch Mar 26, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment