Return-Path: Delivered-To: apmail-harmony-commits-archive@www.apache.org Received: (qmail 78926 invoked from network); 29 Aug 2007 00:34:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 29 Aug 2007 00:34:01 -0000 Received: (qmail 10825 invoked by uid 500); 29 Aug 2007 00:33:57 -0000 Delivered-To: apmail-harmony-commits-archive@harmony.apache.org Received: (qmail 10802 invoked by uid 500); 29 Aug 2007 00:33:57 -0000 Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@harmony.apache.org Delivered-To: mailing list commits@harmony.apache.org Received: (qmail 10793 invoked by uid 99); 29 Aug 2007 00:33:57 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Aug 2007 17:33:56 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Aug 2007 00:33:50 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 82D4371403E for ; Tue, 28 Aug 2007 17:33:30 -0700 (PDT) Message-ID: <28316429.1188347610526.JavaMail.jira@brutus> Date: Tue, 28 Aug 2007 17:33:30 -0700 (PDT) From: "Ilya Berezhniuk (JIRA)" To: commits@harmony.apache.org Subject: [jira] Updated: (HARMONY-4689) [drlvm][jvmti] JVMTI Extension: Native Code Access Interface (NCAI) implementation In-Reply-To: <18468561.1188347490524.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HARMONY-4689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Berezhniuk updated HARMONY-4689: ------------------------------------- Attachment: ncai_bulk.zip > [drlvm][jvmti] JVMTI Extension: Native Code Access Interface (NCAI) implementation > ---------------------------------------------------------------------------------- > > Key: HARMONY-4689 > URL: https://issues.apache.org/jira/browse/HARMONY-4689 > Project: Harmony > Issue Type: New Feature > Components: Contributions, DRLVM > Reporter: Ilya Berezhniuk > Attachments: ncai_bulk.zip > > > The contribution consists of the following component: > - Native Code Access Interface (NCAI) implementation > JVMTI enables debugging of Java frames but ignores native frames (e.g., frames within JNI code). NCAI is a prototype JVMTI extension interface that allows the VM to participate in debugging operations on native code as well. At EclipseCon 2007, we demoed this NCAI component along with a seamless mixed Java/JNI debugger that consumes this interface for an Eclipse extension (http://www.eclipsecon.org/2007/index.php?page=sub/&id=4129). We wanted to donate this component which was prototyped using Apache Harmony so that it could help (a) promote mixed Java/JNI debugging discussions and (b) be harvested for potential additional uses within Apache Harmony. > Below are some details on NCAI implementation. > 1) Basic features provided by the current NCAI implementation: > - Setting breakpoints in native code > - Single stepping through native code with 3 step modes: STEP_INTO, STEP_OVER and STEP_OUT > - Trapping OS-level signals/exceptions > - Trapping loading and unloading of dynamic/shared libraries > - Getting information about loaded dynamic/shared libraries > - Getting list of threads running in VM process > - OS-level threads suspending/resuming/terminating > - Processor registers inspection and modification (for suspended threads) > - Getting call stack for suspended threads including both Java and native frames > - Memory inspection and modification > - Getting OS-level signals/exceptions information > 2) Harmony base: > - Bulk contains a patch for existing DRLVM code and a set of new files arranged with DRLVM directory structure > - Patch was rebased to apply over DRLVM revision r567700 > 3) Current implementation provides all the features listed above for IA-32 architecture only. DRLVM remains buildable on other platforms, but not all the features will work. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.