Return-Path: Delivered-To: apmail-harmony-commits-archive@www.apache.org Received: (qmail 83940 invoked from network); 5 Mar 2008 17:48:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 5 Mar 2008 17:48:57 -0000 Received: (qmail 9294 invoked by uid 500); 5 Mar 2008 17:48:53 -0000 Delivered-To: apmail-harmony-commits-archive@harmony.apache.org Received: (qmail 9270 invoked by uid 500); 5 Mar 2008 17:48:53 -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 9261 invoked by uid 99); 5 Mar 2008 17:48:53 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Mar 2008 09:48:53 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Mar 2008 17:48:12 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id C3803234C08F for ; Wed, 5 Mar 2008 09:47:40 -0800 (PST) Message-ID: <1577617721.1204739260799.JavaMail.jira@brutus> Date: Wed, 5 Mar 2008 09:47:40 -0800 (PST) From: "Vladimir Beliaev (JIRA)" To: commits@harmony.apache.org Subject: [jira] Commented: (HARMONY-5576) [drlvm][jvmti] breakpoints are broken by r633414 - regression In-Reply-To: <822353251.1204739141533.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-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575432#action_12575432 ] Vladimir Beliaev commented on HARMONY-5576: ------------------------------------------- BTW, the simple reproduction way: svn co https://svn.apache.org/repos/asf/harmony/enhanced/buildtest/trunk/tests/vts/vm/src/test/vm/jvmti/share/ . svn co https://svn.apache.org/repos/asf/harmony/enhanced/buildtest/trunk/tests/vts/vm/src/test/vm/jvmti/events/SingleStep/SingleStep0101/ mv SingleStep0101/SingleStep0101.* . rm -fr SingleStep0101/ gcc -shared -fPIC -I -DLINUX -o libSingleStep0101.so SingleStep0101.cpp events.cpp utils.cpp vim SingleStep0101.java # comment package javac SingleStep0101.java /bin/java -agentpath:libSingleStep0101.so SingleStep0101 > [drlvm][jvmti] breakpoints are broken by r633414 - regression > ------------------------------------------------------------- > > Key: HARMONY-5576 > URL: https://issues.apache.org/jira/browse/HARMONY-5576 > Project: Harmony > Issue Type: Bug > Environment: SLES10 x86_64, Harmony release build > Reporter: Vladimir Beliaev > Priority: Blocker > > According to http://people.apache.org/~mloenko/snapshot_testing/script/r633628/index.html the JVMTI-based debugging is broken by recent commits. > The guilty one is r633414: > Applied patches 0011 and 0012 from HARMONY-5504 > [drlvm][port] Restructure DRLVM's sources to extract most of platform dependent code into portlib > The reported failed tests are (I've used SingleStep0101 to find a gulity commit) > VTS VM: > vm.jvmti.events.Breakpoint.Breakpoint0101 > vm.jvmti.events.SingleStep.SingleStep0101 > vm.jvmti.funcs.ClearBreakpoint.ClearBreakpoint0102 > vm.jvmti.funcs.ClearBreakpoint.ClearBreakpoint0104 > vm.jvmti.funcs.ClearBreakpoint.ClearBreakpoint0105 > vm.jvmti.funcs.SetBreakpoint.SetBreakpoint0101 > vm.jvmti.funcs.SetBreakpoint.SetBreakpoint0103 > EUT/jdtdebug: > ok, too many to bee listed here - just please see http://people.apache.org/~smishura/r633628/Linux_x86_64/eut33/results/html/org.eclipse.jdt.debug.tests_linux.gtk.x86_64.html > JDWP suites: > same story, see: > http://people.apache.org/~smishura/r633628/Linux_x86_64/jdktools-test/ > Let's revert the stability killer patch! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.