Timeline for Why do many exception messages not contain useful details?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 28, 2015 at 21:21 | comment | added | Mason Wheeler | chances are the users will never write it down... and you will be told "Well it said something about a violation..." This is why you use an exception logging tool to automatically generate the error report containing the stack trace and possibly even send it to your server. I had one user one time who was not very technical. Every time she would submit a message from the error logger, it would go something like "I'm not sure what I did wrong, but..." no matter how many times I explained that this error meant the bug was on my side. But, I always got the error reports from her! | |
| Apr 15, 2015 at 11:55 | comment | added | Odalrick | "...you would not believe our surprise when virtually EVERY SINGLE FATAL ERROR was return code 101." You're right. I would not belive you were surprised when the contractor followed your instructions. | |
| Apr 14, 2015 at 7:05 | history | edited | Randy | CC BY-SA 3.0 | Just added another real world example of the discussion topic |
| Apr 14, 2015 at 6:52 | review | First posts | |||
| Apr 14, 2015 at 13:13 | |||||
| Apr 14, 2015 at 6:52 | history | answered | Randy | CC BY-SA 3.0 |