harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gregory Shimansky (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HARMONY-2482) [drlvm][exception][class unloading] StackTraceFrame should be refactored
Date Wed, 16 May 2007 13:14:16 GMT

     [ https://issues.apache.org/jira/browse/HARMONY-2482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Gregory Shimansky updated HARMONY-2482:

    Summary: [drlvm][exception][class unloading] StackTraceFrame should be refactored  (was:
[drlvm] StackTraceFrame should be refactored)

> [drlvm][exception][class unloading] StackTraceFrame should be refactored
> ------------------------------------------------------------------------
>                 Key: HARMONY-2482
>                 URL: https://issues.apache.org/jira/browse/HARMONY-2482
>             Project: Harmony
>          Issue Type: Task
>          Components: DRLVM
>            Reporter: Aleksey Ignatenko
>            Priority: Minor
> StackState is a java object wich can save stack state on some moment. It
> contains jlong array of pointers to StackTraceFrame. StackTraceFrame has
> reference to Method. Potentially it could lead to the problem that someone
> tries to restore stack trace with some method of unloaded class. It will lead
> to crash! I suppose that StackTraceFrame should contain method name, line
> number and something else instead of pointer to Method. Or if it is impossible
> - prohibit to restore stack trace by StackState in all places except the top of
> that stack.

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

View raw message