You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Eugene S. Ostrovsky (JIRA)" <ji...@apache.org> on 2007/08/27 13:53:31 UTC

[jira] Commented: (HARMONY-4335) [buildtest][vts] Test vm/jvmti/funcs/GetMethodName/GetMethodName0102/GetMethodName0102.xml crashes on printing wrong data

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

Eugene S. Ostrovsky commented on HARMONY-4335:
----------------------------------------------

The test should be in exclude list.
Although fixed the test doesn''t work in DRLVM since HARMONY-4404.(3).

Gregory, please add the following line to /harmony/enhanced/buildtest/branches/2.0/tests/vts/vm/config/exclude.file :
vm/jvmti/funcs/GetMethodName/GetMethodName0102/GetMethodName0102.xml

> [buildtest][vts] Test vm/jvmti/funcs/GetMethodName/GetMethodName0102/GetMethodName0102.xml crashes on printing wrong data
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HARMONY-4335
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4335
>             Project: Harmony
>          Issue Type: Bug
>          Components: build - test - ci
>            Reporter: Vera Petrashkova
>            Assignee: Gregory Shimansky
>         Attachments: GetMethodName0102.patch
>
>
> Test vm/jvmti/funcs/GetMethodName/GetMethodName0102/GetMethodName0102.xml checks that 
> GetMethodName method returns JVMTI_ERROR_INVALID_METHODID (23) when used parameter is not
> jmethodID.
> It invokes this method with incorrect argument and then tries to report data which were not defined.
> See source code:
> ---------GetMethodName0102.cpp-------------
> void JNICALL callbackException(prms_EXCPT)
> {
>     check_EXCPT;
>     if (flag) return;
>     char* name;
>     char* signature;
>     char* generic;
>     jvmtiError result;
>     jvmtiPhase phase;
>     result = jvmti_env->GetPhase(&phase);
>     if ((result != JVMTI_ERROR_NONE) || (phase != JVMTI_PHASE_LIVE)) return;
>     fprintf(stderr, "\tnative: GetPhase result = %d (must be zero) \n", result);
>     fprintf(stderr, "\tnative: current phase is %d (must be 4 (LIVE-phase)) \n", phase);
>     result = jvmti_env->GetMethodName((jmethodID)jvmti_env, &name, &signature, &generic);
>     fprintf(stderr, "\tnative: GetMethodName result = %d (must be JVMTI_ERROR_INVALID_METHODID (23)) \n", result);
>     fprintf(stderr, "\tnative: method name is %s \n", name);                           <<<< should be removed
>     fprintf(stderr, "\tnative: signature name is %s \n", signature);                    <<<< should be removed
>     fprintf(stderr, "\tnative: generic name is %s \n", generic);                         <<<< should be removed
>     fflush(stderr);
>     if (result != JVMTI_ERROR_INVALID_METHODID) return;
>     flag = true;
>     util = true;
>     test = true;
> }
> ----------------------------------
> As the result RI return correct error code and then crashes when it tries to report undefined information about the method.
> This problem which causes the failure of this test on Harmony 
> is now listed in drlvm known issues and limitations on the Harmony
> page http://wiki.apache.org/harmony/KnownNonBugIssuesAndLimitations

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