• Almafuerte (unregistered)

    Still, the real WTF is using ASP.

  • (cs) in reply to Ed
    Ed:
    Mcoder:
    And, I'm sad, I can't one-up this one. The worst case of error handling I've seen is the logger initializing trying to log its errors to the logger it is initializing.

    That reminds me of the error handler that tried to look up the translation for 'no connection to database' in the database it could not connect to.

    Or Microsoft Enterprise Library, which logs errors writing to the event log for your application's errors by... logging an event to the event log with the stack trace of the error it encountered logging the error.

  • Sorin (unregistered)

    Or you can use www.exceptiontail.com :)

  • Daniel (unregistered)

    About the last statement: Most, if not all, Microsoft-ified languages revert to the default system error handler when an error occurs within the error handler. I know from personal experience with Visual Basic and Visual FoxPro (yes, someone actually still uses it unfortunately) if an error occurs within someone's custom error handler, you just get the default "run time error blah blah blah" and app close. No recursive spiral of death.

    But I've never coded anything in ASP.

Leave a comment on “Error-prone Errors”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article