Philipp Oppermann 9963961f35 Test the handler_with_error_code macro in a different way ...

We now take stack_frame as a immutable reference and we shouldn't write to a &. So the old test example (page faults as breakpoints) becomes even more hacky. Instead, we're now deliberately entering an endless page fault loop to check our iretq logic.

2016-11-01 17:50:51 +01:00

..

01-multiboot-kernel.md

Rename posts: Use ascending numbers instead of date

2016-09-18 19:25:08 +02:00

02-entering-longmode.md

Remove old “Update” sections (#244)

2016-10-15 17:10:43 +02:00

03-set-up-rust.md

Remove old “Update” sections (#244)

2016-10-15 17:10:43 +02:00

04-printing-to-screen.md

Improve wording and add some more QEMU screenshots

2016-10-30 17:23:17 +01:00

05-allocating-frames.md

Remove old “Update” sections (#244)

2016-10-15 17:10:43 +02:00

06-page-tables.md

Page Tables: clarify that we need to map the P4 table recursively before enabling paging (#246)

2016-10-23 16:04:09 +02:00

07-remap-the-kernel.md

therefor -> for that

2016-10-31 15:31:32 +01:00

08-kernel-heap.md

Minor wording change

2016-09-22 16:03:32 -06:00

09-catching-exceptions.md

Fix typo

2016-10-30 19:12:55 +01:00

10-better-exception-messages.md

Better Exception Messages: Take stack_frame argument as reference

2016-11-01 17:46:57 +01:00

11-returning-from-exceptions.md

Test the handler_with_error_code macro in a different way

2016-11-01 17:50:51 +01:00