Ask HN: Imagine worse then error handling with sloppy exception handling?

So I have been dealing with a complied closed source program that fails in a grandious way. It leaves no logs behind, it just kinda blows up. You have to kill -9 it, anything short it does not respond to.

A coworker had this horrible thought that cases me to hate the world... he said- what if the logging function they use to write an error log has a trackback in itself and it has a global catch all in it so essentially it recursively is calling itself preventing any log output from happening but also maxing out the processor.

This thought gave me a headache, since exception handling and recursivness both are highly touchy subjects to any seasoned programmer. Fuck, might as well include character encoding and cache invalidation to make the perfect storm...

I will not mention this software writers since it's quite prevalent in all fortune 500 companies. Just gotta vent.