Bug 2202 - Apparently unnecessary catch(Throwable)s
Apparently unnecessary catch(Throwable)s
Status: NEW
Product: jogl
Classification: Unclassified
Component: source
All All
: P5 minor
: ---
Assigned To: Sven Gothel
Depends on:
  Show dependency treegraph
Reported: 2010-03-10 22:36 UTC by redlizard
Modified: 2010-03-10 22:36 UTC (History)
1 user (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description redlizard 2010-03-10 22:36:03 UTC
At several places in the source, catch(Throwable) is used for no reason that I've been able to uncover. This, of course, has the nasty effect of hiding certain severe errors that should normally abort the VM (and dump a stacktrace) immediately - in my case, a NoClassDefFoundError due to a filename typo somewhere, but most Errors qualify for this treatment.

Is there a good reason all Throwables are often caught instead of only Exceptions? If not, it should probably be replaced by more debugging-friendly error checking.