Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Message-ID: <3552767.1186741783217.JavaMail.jira@brutus>
Date: Fri, 10 Aug 2007 03:29:43 -0700 (PDT)
From: "Alexey Varlamov (JIRA)" <jira@apache.org>
To: commits@harmony.apache.org
Subject: [jira] Closed: (HARMONY-3670) [drlvm][classloader][classparser]
 misleading messages for truncated classfile
In-Reply-To: <5603302.1176787635298.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HARMONY-3670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Varlamov closed HARMONY-3670.
------------------------------------

    Resolution: Fixed

Fixed by HARMONY-4247

> [drlvm][classloader][classparser] misleading messages for truncated classfile
> -----------------------------------------------------------------------------
>
>                 Key: HARMONY-3670
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3670
>             Project: Harmony
>          Issue Type: Sub-task
>          Components: DRLVM
>            Reporter: Alexey Varlamov
>            Priority: Trivial
>
> I noticed DRLVM gives misguiding message in case of truncated classfile, like " could not parse bla-bla-bla", while RI plainly says "Truncated classfile". 
> Really, this is widely used pattern in Class_File_Loader.cpp, like 
> if(!cfs.parse(&value)) { 
>   REPORT_FAILED_CLASS("could not parse bla-bla value"); 
>   return false; 
> } 
> for each and every entity. Quite verbose and not really useful, we need to refactor this. 

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