harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geir Magnusson Jr (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HARMONY-1545) [drlvm] [jvmti] Unified JVMTI breakpoints infrastructure implementation
Date Sat, 23 Sep 2006 13:17:24 GMT
     [ http://issues.apache.org/jira/browse/HARMONY-1545?page=all ]

Geir Magnusson Jr updated HARMONY-1545:

    Component/s: DRLVM

please ensure that patches/issues for DRLVM are put into that category

> [drlvm] [jvmti] Unified JVMTI breakpoints infrastructure implementation
> -----------------------------------------------------------------------
>                 Key: HARMONY-1545
>                 URL: http://issues.apache.org/jira/browse/HARMONY-1545
>             Project: Harmony
>          Issue Type: Improvement
>          Components: DRLVM
>            Reporter: Ilya Berezhniuk
>         Attachments: JVMTI-breakpoints-unified-infrastructure.patch
> Hello
> I've reworked the implementation of JVMTI breakpoints and single step. The code which
sends breakpoint and single step events currently is ugly and uses unobvious logic. In the
new implementation the infrastructure is much more clean and clear :)
> Main class is VMBreakPoints. It is the container for all breakpoint instrumentation and
handler for all breakpoint events. A VMBreakInterface is a class for breakpoints references
container. It can be used for any purpose, be it SingleStep or user breakpoints container.
In VMBreakInterface breakpoints instrumentations are referenced by VMBreakPointRef.
> VMBreakPoints has handlers for native (JIT mode) and interpreter mode breakpoints. When
such handler is called, the processing goes through all registered VMBreakInterface instances
according to their priorities (currently two priorities are supported - SingleStep is first
according to JVMTI spec about colocated events) and calls VMBreakInterface handling callback
which can send an event of type which this interface supports.

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


View raw message