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 2006/12/27 11:44:21 UTC
[jira] Created: (HARMONY-2893) [jdktools][jdwp] remove workaround
for JVMTI GetStackTrace() problem
[jdktools][jdwp] remove workaround for JVMTI GetStackTrace() problem
--------------------------------------------------------------------
Key: HARMONY-2893
URL: http://issues.apache.org/jira/browse/HARMONY-2893
Project: Harmony
Issue Type: Bug
Components: JDK
Reporter: Ivan Popov
There were noticed problems with implementation of JVMTI function GetStackTrace in some JVMs, it may ignore 'start_depth' parameter and return stack frames always starting from 0. Implementation of JDWP commands ThreadReference::Frames and StackFrame.ThisObject provides workaround for this problem by requesting from JVMTI all stack frames and removing not interesting ones from the list. Though this increases usability of Harmony JDWP agent with different JVMs, it may negatively affect performance. It makes sense to check how this workaround affect real performance to decide if it worth to be removed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (HARMONY-2893) [jdktools][jdwp] remove workaround
for JVMTI GetStackTrace() problem
Posted by "Ivan Popov (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-2893?page=all ]
Ivan Popov updated HARMONY-2893:
--------------------------------
Estimated Complexity: Novice
Priority: Minor (was: Major)
> [jdktools][jdwp] remove workaround for JVMTI GetStackTrace() problem
> --------------------------------------------------------------------
>
> Key: HARMONY-2893
> URL: http://issues.apache.org/jira/browse/HARMONY-2893
> Project: Harmony
> Issue Type: Bug
> Components: JDK
> Reporter: Ivan Popov
> Priority: Minor
>
> There were noticed problems with implementation of JVMTI function GetStackTrace in some JVMs, it may ignore 'start_depth' parameter and return stack frames always starting from 0. Implementation of JDWP commands ThreadReference::Frames and StackFrame.ThisObject provides workaround for this problem by requesting from JVMTI all stack frames and removing not interesting ones from the list. Though this increases usability of Harmony JDWP agent with different JVMs, it may negatively affect performance. It makes sense to check how this workaround affect real performance to decide if it worth to be removed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (HARMONY-2893) [jdktools][jdwp] remove workaround
for JVMTI GetStackTrace() problem
Posted by "Ivan Popov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivan Popov updated HARMONY-2893:
--------------------------------
Issue Type: Improvement (was: Bug)
> [jdktools][jdwp] remove workaround for JVMTI GetStackTrace() problem
> --------------------------------------------------------------------
>
> Key: HARMONY-2893
> URL: https://issues.apache.org/jira/browse/HARMONY-2893
> Project: Harmony
> Issue Type: Improvement
> Components: JDK
> Reporter: Ivan Popov
> Priority: Minor
>
> There were noticed problems with implementation of JVMTI function GetStackTrace in some JVMs, it may ignore 'start_depth' parameter and return stack frames always starting from 0. Implementation of JDWP commands ThreadReference::Frames and StackFrame.ThisObject provides workaround for this problem by requesting from JVMTI all stack frames and removing not interesting ones from the list. Though this increases usability of Harmony JDWP agent with different JVMs, it may negatively affect performance. It makes sense to check how this workaround affect real performance to decide if it worth to be removed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.