Timeline for Why should 'boneheaded' exceptions not be caught, especially in server code?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 16, 2020 at 9:43 | audit | First posts | |||
| Jan 17, 2020 at 17:47 | |||||
| Jan 13, 2020 at 17:22 | audit | First posts | |||
| Jan 13, 2020 at 17:23 | |||||
| S Jan 7, 2020 at 16:35 | history | suggested | Toby Speight | CC BY-SA 4.0 |
Spelling and grammar
|
| Jan 7, 2020 at 15:28 | review | Suggested edits | |||
| S Jan 7, 2020 at 16:35 | |||||
| Jan 7, 2020 at 13:27 | comment | added | JacquesB | @cmaster-reinstatemonica Obviosuly a .net exception can never escape the CLR. My point is that even if the web server was written in .net, you wouldn't let an exception in a request handler take down the whole server. You do want to catch all exceptions, even boneheaded ones. You just have to do it at the right level. | |
| Jan 6, 2020 at 20:36 | comment | added | cmaster - reinstate monica | "If we followed to never catch "boneheaded exceptions", then a single application bug should bubble up and cause the whole operating system to crash." Sorry, that's just plain wrong. An exception cannot bubble out of its process. To the kernel, a throw, stack-unwind, catch is just a bunch of machine code like the rest it loaded from the binary. And the process's internal state, that which can be inconsistent due to an error, is none of the kernel's concern. To the kernel it's just some memory pages that are allocated to the process. That separation is the main reason we use virtual memory. | |
| Jan 5, 2020 at 23:11 | history | edited | JacquesB | CC BY-SA 4.0 |
added 309 characters in body
|
| Jan 5, 2020 at 12:35 | history | answered | JacquesB | CC BY-SA 4.0 |