|
From: | Steven Augart |
Subject: | Re: Query on stacktrace management logic |
Date: | Tue, 02 Mar 2004 00:50:04 -0500 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113 |
David Holmes wrote:
I still need a hook to not get the stacktrace filled in for OutOfMemoryError - though perhaps I can do something without requiring allocation using a different approach.
In Jikes RVM, we override a few of Classpath's implementations; we have our own Object.java and (relevant to your case) Throwable.java, for instance. Hope this helps.
The biggest ugliness here is that the version the rest of Classpath sees is not the same one as will actually be loaded at run time. One day this will probably bite us when Classpath adds some new (Java 1.5 or 1.6?) method or field to a class we override before we do it ourselves, and some other Classpath class uses the new method or field.
--Steve Augart -- Steven Augart Jikes RVM, open source Research Virtual Machine: http://oss.software.ibm.com/jikesrvm Office: +1 914/784-6743 T.J. Watson Research Center, IBM
[Prev in Thread] | Current Thread | [Next in Thread] |