Why is there “Unknown error” in real life? [duplicate]
This question already has answers here: How much information about an error should be shown to the user? (6 answers) Closed 9 years ago. As a programmer, I always try my best to explain what happened in the code when I have to show an error message, for example: try { int a = b […]
Why is there “Unknown error” in real life? [duplicate]
This question already has answers here: How much information about an error should be shown to the user? (6 answers) Closed 9 years ago. As a programmer, I always try my best to explain what happened in the code when I have to show an error message, for example: try { int a = b […]
Why is there “Unknown error” in real life? [duplicate]
This question already has answers here: How much information about an error should be shown to the user? (6 answers) Closed 9 years ago. As a programmer, I always try my best to explain what happened in the code when I have to show an error message, for example: try { int a = b […]
Why is there “Unknown error” in real life? [duplicate]
This question already has answers here: How much information about an error should be shown to the user? (6 answers) Closed 9 years ago. As a programmer, I always try my best to explain what happened in the code when I have to show an error message, for example: try { int a = b […]
My value checker function needs to return both a boolean and a message
I have a value checking function, something much like a credit card number checking function, that is passed in a string, and needs to check that the value is of the right format.
What an application should do when there is an error notifying the user of an error?
Say I have an application, and it writes (among other things) errors to a log file. It’s the first place the user would be asked to go and look if there was a problem. Let’s also assume that this is a critical application that cannot be allowed to just crash.
Protect memory from a potentially seg faulting function call
How can one safely call a function that might segfault without corrupting the stack or the heap?
Protect memory from a potentially seg faulting function call
How can one safely call a function that might segfault without corrupting the stack or the heap?
Protect memory from a potentially seg faulting function call
How can one safely call a function that might segfault without corrupting the stack or the heap?
Testing generic errors
I’ve got a program that validates it’s input, and then errors.