You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Vladimir Beliaev (JIRA)" <ji...@apache.org> on 2008/03/05 18:45:41 UTC
[jira] Created: (HARMONY-5576) [drlvm][jvmti] breakpoints are
broken by r633414 - regression
[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.
[jira] Commented: (HARMONY-5576) [drlvm][jvmti] breakpoints are
broken by r633414 - regression
Posted by "Vladimir Beliaev (JIRA)" <ji...@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<path to jvmti.h> -DLINUX -o libSingleStep0101.so SingleStep0101.cpp events.cpp utils.cpp
vim SingleStep0101.java # comment package
javac SingleStep0101.java
<harmony>/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.
[jira] Commented: (HARMONY-5576) [drlvm][jvmti] breakpoints are
broken by r633414 - regression
Posted by "Ilya Berezhniuk (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575496#action_12575496 ]
Ilya Berezhniuk commented on HARMONY-5576:
------------------------------------------
The patch fixes all SingleStep and PopFrame JDWP tests.
It's strange but the bug does not appear on debug build. That's why it was not catched by th pre-commit suites.
> [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
> Attachments: H-5576.patch
>
>
> 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.
[jira] Resolved: (HARMONY-5576) [drlvm][jvmti] breakpoints are
broken by r633414 - regression
Posted by "Gregory Shimansky (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gregory Shimansky resolved HARMONY-5576.
----------------------------------------
Resolution: Fixed
Assignee: Gregory Shimansky
Patch is applied at 634034. Please check that tests work now.
> [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
> Assignee: Gregory Shimansky
> Priority: Blocker
> Attachments: H-5576.patch
>
>
> 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.
[jira] Updated: (HARMONY-5576) [drlvm][jvmti] breakpoints are
broken by r633414 - regression
Posted by "Ilya Berezhniuk (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ilya Berezhniuk updated HARMONY-5576:
-------------------------------------
Attachment: H-5576.patch
I've attached the patch fixing the problem with mentioned VTS test.
The bug was because of copy-pasted code from Windows, where I changed RCX to RDI (1st arg on Linux) in one place and forgot 2nd place.
Sorry for inconvinience.
I'm also going to check the patch on JDWP tests; I'll report results a bit later.
> [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
> Attachments: H-5576.patch
>
>
> 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.