[jira] Commented: (HARMONY-6245) NoSuchMethod error with three-level hierarchy

["Pavel Pervov (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HARMONY-6245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723958#action_12723958 ] 

Pavel Pervov commented on HARMONY-6245:
---------------------------------------

Without looking at the code I may suggest that the problem is in the fact that DRLVM contains antlr and uses it for internal purposes and that antlr can have older version, which does not contain resetTokenBuffer()V with this exact signature or does not contain it at all.

Try using -Xbootclasspath/p:<path to your antlr>. If this fixes the issue, we can look at updating antlr version used in DRLVM to the latest version.

Otherwise, it is necessary to debug the whole thingy (is it SAP over Harmony?).

> NoSuchMethod error with three-level hierarchy
> ---------------------------------------------
>
>                 Key: HARMONY-6245
>                 URL: https://issues.apache.org/jira/browse/HARMONY-6245
>             Project: Harmony
>          Issue Type: Bug
>          Components: VM
>    Affects Versions: 5.0M10
>         Environment: Windows XP SP2 32bit
> C:\jdk\harmony-jdk-782693\bin>java -version
> Apache Harmony Launcher : (c) Copyright 1991, 2009 The Apache Software Foundation or its licensors, as applicable.
> java version "1.5.0"
> pre-alpha : not complete or compatible
> svn = r782693, (Jun 12 2009), Windows/ia32/msvc 1310, release build
> http://harmony.apache.org
>            Reporter: Hristo Spaschev Iliev
>         Attachments: NoSuchMethod.zip
>
>
> Running the attached class produces:
>   java.lang.NoSuchMethodError: com/sap/sql/sqlparser/SQLParser.resetTokenBuffer()V while resolving constant pool entry at index 9 in class Test
>           at Test.main(Test.java:13)
> The hierarchy used is:
>    public class SQLParser extends LLkParser 
>    public class LLkParser extends Parser
> The method resetTokenBuffer() however can be found in antlr.Parser
> Running the same with SunVM produces no such Error

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