harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gregory Shimansky (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-4724) [drlvm][EUT] EUT 3.2 jdtdebug suite reports 'Program did not suspend'
Date Tue, 18 Sep 2007 15:59:43 GMT

    [ https://issues.apache.org/jira/browse/HARMONY-4724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12528422

Gregory Shimansky commented on HARMONY-4724:

I think the target program simply crashes when it is executed. The problem is that when WatchExpressionTests
tries to do StepOver, an assertion fires in JVMTI code:


The reference in class' constant pool is not resolved. This reference is from WatchItemTests
class to Integer.<init> method. It is not resolved because it is called for the first
time, and now that we have lazy resolution it is supposed to be resolved inside of call to
classloader while executing invokespecial bytecode.

If I press continue in debugger for the first time instead of stepping over, method is resolved,
and I can happily step over inside of the loop of fillVector method.

Now it is necessary to understand how to adapt JVMTI single step code to the lazy resolution
of static and special methods.

> [drlvm][EUT] EUT 3.2 jdtdebug suite reports 'Program did not suspend'
> ---------------------------------------------------------------------
>                 Key: HARMONY-4724
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4724
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>         Environment: Eclipse 3.2.1
>            Reporter: Ilya Berezhniuk
> Several failures with mesages like "Program did not suspend" or "Program did not suspend,
launch terminated" have appeared recently in jdtdebug suite (EUT 3.2). Stack looks like this:
> --------------------------
> Program did not suspend. 
> junit.framework.AssertionFailedError: Program did not suspend.
> at org.eclipse.jdt.debug.tests.AbstractDebugTest.stepReturn(AbstractDebugTest.java:1205)
> at org.eclipse.jdt.debug.tests.core.ConditionalBreakpointsTests.testConditionalStepReturn(ConditionalBreakpointsTests.java:120)
> at java.lang.reflect.VMReflection.invokeMethod(VMReflection.java)
> at org.eclipse.jdt.debug.tests.DebugSuite$1.run(DebugSuite.java:53)
> at java.lang.Thread.run(Thread.java:662)
> --------------------------
> I've tried to locate commit introduced these failures - looks like it's 570541 commit
for HARMONY-4661.
> This commit doesn't affect EUT 3.3.
> --------------------------
> To reproduce:
> 1. Follow items 1,2,4 from http://wiki.apache.org/harmony/Eclipse_Unit_Tests_Pass_on_DRLVM#How_to_run_EUT_individual
> 2. Add 'org.eclipse.jdt.debug.tests' suite in the 'Selection' dialog
> 3. Open src-javabuildtests and run org.eclipse.jdt.debug.tests suite 'as JUnit Plug-in

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message