Mailing-List: contact harmony-commits-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: harmony-dev@incubator.apache.org
Message-ID: <2438209.1162558879077.JavaMail.root@brutus>
Date: Fri, 3 Nov 2006 05:01:19 -0800 (PST)
From: "Gregory Shimansky (JIRA)" <jira@apache.org>
To: harmony-commits@incubator.apache.org
Subject: [jira] Resolved: (HARMONY-1987) [DRLVM] [JVMTI] Insufficient check
 of fieldID in Field group of JVMTI functions.
In-Reply-To: <28153508.1161951256561.JavaMail.root@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/HARMONY-1987?page=all ]

Gregory Shimansky resolved HARMONY-1987.
----------------------------------------

    Resolution: Fixed

Patch applied at 470792. Please check that it was applied as expected.

> [DRLVM] [JVMTI] Insufficient check of fieldID in Field group of JVMTI functions.
> --------------------------------------------------------------------------------
>
>                 Key: HARMONY-1987
>                 URL: http://issues.apache.org/jira/browse/HARMONY-1987
>             Project: Harmony
>          Issue Type: Improvement
>          Components: DRLVM
>            Reporter: Kostin Mihail
>         Assigned To: Gregory Shimansky
>         Attachments: fieldID_check_for_JVMTI.patch, test.zip
>
>
> Functions from Field group of JVMTI functions crashes if it's called with incorrect fieldID. According to specification function should return JVMTI_ERROR_INVALID_FIELDID (25) in this case.
> This occurs because of insufficient check of fieldID in Field group of JVMTI functions. Those functions have no checking of whether field with this fieldID exists.
> Solution to this problem is to add additional checking of fieldID to know whether this field exists. This checking is as follows: take list of _all_ class fields and its IDs and check whether fieldID is in that list before to start working with it.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira