You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Gregory Shimansky (JIRA)" <ji...@apache.org> on 2006/09/21 02:31:23 UTC

[jira] Updated: (HARMONY-1511) [drlvm] [jvmti] Bugs in field watches and stack trace for JIT, jvmtiGetBytecodes and single step/breakpoints for interpreter

     [ http://issues.apache.org/jira/browse/HARMONY-1511?page=all ]

Gregory Shimansky updated HARMONY-1511:
---------------------------------------

    Attachment: jvmti-watch-stack-method-interpreter-fixes.patch

The patch to fix current problems.

> [drlvm] [jvmti] Bugs in field watches and stack trace for JIT, jvmtiGetBytecodes and single step/breakpoints for interpreter
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HARMONY-1511
>                 URL: http://issues.apache.org/jira/browse/HARMONY-1511
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>            Reporter: Gregory Shimansky
>         Attachments: jvmti-watch-stack-method-interpreter-fixes.patch
>
>
> This is a patch with several small bugfixes for JVMTI unrelated directly to single step implementation. The following problems are fixed:
> - Field watches callback from JIT should have RAISE_AREA set since it is not an unwindable code
> - Stack trace on JIT should skip top level VM internal java methods because they are not supposed to be shown to user
> - Only on interpreter should VM search for breakpoints in the instrumented method bytecode because on JIT this bytecode is not touched, the compiled code is changed instead
> - When running on interpreter SingleStep event should be sent before Breakpoint event according to JVMTI spec. ATM there have reverse order

-- 
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