You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Ivan Popov (JIRA)" <ji...@apache.org> on 2007/06/20 16:23:26 UTC
[jira] Updated: (HARMONY-2912) [jdktools][jdwp] Improve
METHOD_ENTRY/METHOD_EXIT handlers
[ https://issues.apache.org/jira/browse/HARMONY-2912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivan Popov updated HARMONY-2912:
--------------------------------
Issue Type: Improvement (was: Bug)
> [jdktools][jdwp] Improve METHOD_ENTRY/METHOD_EXIT handlers
> ----------------------------------------------------------
>
> Key: HARMONY-2912
> URL: https://issues.apache.org/jira/browse/HARMONY-2912
> Project: Harmony
> Issue Type: Improvement
> Components: JDK
> Reporter: Ivan Popov
> Priority: Minor
>
> In the current implementation JDWP agent uses GetFrameLocation() for the top stack
> frame to find method location, but gets methodID and classID from jmethodID
> passed to event callback. In usual case this is the same method as reported for
> top stack frame. However, if GetMethodLocation() reports different method,
> agent will put inconsistent information into reply packet.
> Implementation of METHOD_ENTRY/METHOD_EXIT events should be improved to provide
> consistent data or report error if this is not possible. Assertion, currently
> presented in source code, is not a perfect solution.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.