BZ #185: CACAO spits out unsolicited finalizer exceptions

Status fields:

For example, this, which is normally silently ignored:

$ cacao -Xmx256m -jar dacapo-2006-10-MR2.jar antlr
Exception in thread "Finalizer" java.io.IOException: invalid file descriptor
   at gnu.java.nio.VMChannel$State.close(VMChannel.java:695)
   at gnu.java.nio.VMChannel.close(VMChannel.java:625)
   at gnu.java.nio.FileChannelImpl.implCloseChannel(FileChannelImpl.java:218)
   at java.nio.channels.spi.AbstractInterruptibleChannel.close(AbstractInterruptibleChan
nel.java:80)
   at java.io.RandomAccessFile.close(RandomAccessFile.java:183)
   at java.util.zip.ZipFile.close(ZipFile.java:318)
   at java.util.zip.ZipFile.finalize(ZipFile.java:328)
===== DaCapo antlr starting =====

This is caused by the removal of opt_DebugFinalizer in
<http://mips.complang.tuwien.ac.at/hg/cacao/rev/5cce362cb59e>.

The reason seems to be that exceptions_print_stacktrace() is not filtered by the logging
framework the way that LOG(...) is.

The #if !defined(NDEBUG) in
http://mips.complang.tuwien.ac.at/hg/cacao/rev/5cce362cb59e#l1.62 should be changed to
if (DEBUG_COND). Unfortunately DEBUG_COND is currently broken in the staging repo. I'll
prepare a patch for this issue and create a pull request together with my DEBUG_* macro
fixes.

Resolved:
http://mips.complang.tuwien.ac.at/hg/cacao/rev/288603e79fc64d0a7f02a6c20b1e0f2173c1d6b6