Return-Path: Delivered-To: apmail-incubator-harmony-dev-archive@www.apache.org Received: (qmail 66087 invoked from network); 23 Sep 2006 14:47:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 23 Sep 2006 14:47:05 -0000 Received: (qmail 69556 invoked by uid 500); 23 Sep 2006 14:47:04 -0000 Delivered-To: apmail-incubator-harmony-dev-archive@incubator.apache.org Received: (qmail 68877 invoked by uid 500); 23 Sep 2006 14:47:03 -0000 Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: harmony-dev@incubator.apache.org Delivered-To: mailing list harmony-dev@incubator.apache.org Received: (qmail 68866 invoked by uid 99); 23 Sep 2006 14:47:03 -0000 Received: from idunn.apache.osuosl.org (HELO idunn.apache.osuosl.org) (140.211.166.84) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 23 Sep 2006 07:47:03 -0700 Authentication-Results: idunn.apache.osuosl.org smtp.mail=pmcfirst@gmail.com; spf=pass Authentication-Results: idunn.apache.osuosl.org header.from=pmcfirst@gmail.com; domainkeys=good X-ASF-Spam-Status: No, hits=2.5 required=5.0 tests=DNS_FROM_RFC_ABUSE,HTML_MESSAGE Received-SPF: pass (idunn.apache.osuosl.org: domain gmail.com designates 64.233.166.180 as permitted sender) DomainKey-Status: good X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 Received: from [64.233.166.180] ([64.233.166.180:8587] helo=py-out-1112.google.com) by idunn.apache.osuosl.org (ecelerity 2.1.1.8 r(12930)) with ESMTP id BD/4D-27820-6E845154 for ; Sat, 23 Sep 2006 07:47:02 -0700 Received: by py-out-1112.google.com with SMTP id c30so1783424pyc for ; Sat, 23 Sep 2006 07:46:59 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=ET+DCioxDkZ9rfBvirUgSJGCXWGmhN2iW9kWHjjCl8X4v2fMdeFC0U9z1aCiB+GTHP3LCsMm9lGdYLci4kTYArollDTwZYDImq9DonO7haXUzE++VpMLRbMevYZ8UXx8uWlUO12HUckhDno1CgO9M5zYNURitTi3+wPhL0i5JRc= Received: by 10.35.41.14 with SMTP id t14mr3842260pyj; Sat, 23 Sep 2006 07:46:59 -0700 (PDT) Received: by 10.35.31.10 with HTTP; Sat, 23 Sep 2006 07:46:59 -0700 (PDT) Message-ID: Date: Sat, 23 Sep 2006 18:46:59 +0400 From: "Pavel Pervov" To: harmony-dev@incubator.apache.org Subject: Re: [jira] Closed: (HARMONY-1545) [drlvm] [jvmti] Unified JVMTI breakpoints infrastructure implementation Cc: harmony-commits@incubator.apache.org In-Reply-To: <5778390.1159018063497.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_6354_22567229.1159022819223" References: <17259913.1158929302379.JavaMail.jira@brutus> <5778390.1159018063497.JavaMail.jira@brutus> X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_6354_22567229.1159022819223 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Geir, Looks like you've missed adding file enhanced/drlvm/trunk/vm/vmcore/include/jvmti_break_intf.h to SVN tree. Regards, Pavel. On 9/23/06, Geir Magnusson Jr (JIRA) wrote: > > [ http://issues.apache.org/jira/browse/HARMONY-1545?page=all ] > > Geir Magnusson Jr closed HARMONY-1545. > -------------------------------------- > > > > [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 > > Assigned To: Geir Magnusson Jr > > 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 > > > ------=_Part_6354_22567229.1159022819223--