---- Reported by email@example.com 2010-03-22 12:46:25 -0400 ----
---- Reported by firstname.lastname@example.org 2010-03-10 22:36:03 ----
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.
--- Bug imported by email@example.com 2010-03-22 12:46 EDT ---
This bug was previously known as _bug_ 2202 at http://kenai.com/bugzilla/show_bug.cgi?id=2202
Unknown platform all. Setting to default platform "".
The original reporter of this bug does not have
an account here. Reassigning to the person who moved
it here: firstname.lastname@example.org.
Previous reporter was email@example.com.
--- Bug imported by firstname.lastname@example.org 2010-03-24 08:04 EDT ---
This bug was previously known as _bug_ 10 at http://jogamp.org/bugzilla/show_bug.cgi?id=10
Unknown platform unknown. Setting to default platform "".
fix platform and os.
Fixed by various code reviews listed at bug #395
*** This bug has been marked as a duplicate of bug 395 ***