harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Varlamov (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-3845) [DRLVM] Class unloading support in lazy stack creation.
Date Wed, 16 May 2007 04:53:16 GMT

    [ https://issues.apache.org/jira/browse/HARMONY-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496192

Alexey Varlamov commented on HARMONY-3845:

Somewhat encumbered approach IMO, and too heavyweight impl (oversynchronized).
I can think of the following alternatives:
1) To detect if corresponding class is unloaded, keep a pointer to it's ClassLoader in StackTraceFrame.
When trace is requested, just look if the ClassLoader is still in ClassLoaderTable and report
"??:?" otherwise.
2) Instead of keeping MethodHandle in StackTraceFrame, store class and method name Strings
- negligible space overhead and no perf penalty. Even if corresponding class is unloaded,
only line information is lost which is acceptable.

> [DRLVM] Class unloading support in lazy stack creation.
> -------------------------------------------------------
>                 Key: HARMONY-3845
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3845
>             Project: Harmony
>          Issue Type: New Feature
>          Components: DRLVM
>            Reporter: Pavel Afremov
>         Attachments: 0001-First-version-of-class-unloading-support-implementat.patch,
0002-Tune-class-unloading-support-in-lazy-stack-creation.patch, ExceptionsBenchmark.java
> Class unloading support in lazy stack creation.
> When classes are unloaded, stack traces for all exception should be created, because
required information can be unreachable late. Static method "Throwable.createAllStackTraces()
"should be called for it.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message