groovy-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject Re:Re: Illegal type in constant pool
Date Tue, 12 Jul 2016 11:33:27 GMT
@Jochen, that's ok. But can you tell me what's the wrong in the constant pool?
I found even if enable @CompileStatic the stack trace is still thrown:(

At 2016-07-12 18:58:53, "Jochen Theodorou" <> wrote:
>Is it ok for me to forward this to the asm list? Because I think if 
>there is really a constant pool entry that is wrong, then it is probably 
>a bug in asm, since we do not really set constant pool entries directly.
>bye Jcohen
>On 12.07.2016 05:25, NETEASE wrote:
>> hello,I uploaded the stack trace and javap of the class to MediaFire,
>> you can download them from:
>> besides, if I enable @CompileStatic then the problem is gone, please
>> help me to figure out what's wrong.
>> Many thanks~
>> At 2016-07-11 04:08:47, "Jochen Theodorou" <> wrote:
>>>On 10.07.2016 16:30, NETEASE wrote:
>>>> Hi, the following stack trace is thrown when I upgraded groovy(indy)
>>>> from 2.3.11 to 2.4.7 and replaced groovy-eclipse-compiler
>>>> with GMavenPlus which supports INDY feature.
>>>> Caused by: java.lang.VerifyError: (class:
>>>> com/xxx/yyydaemon/ScheduleTransferChannelTask, method: executeTask
>>>> signature:
>>>> (Lcom/xxx/yyy/client/executor/simple/processor/SimpleJobContext;)V)
>>>> Illegal type in constant pool
>>>> the output of javap -v ScheduleTransferChannelTask is the following:
>>>> Classfile
>>>> /home/wangyin.wy/com/xxx/yyydaemon/ScheduleTransferChannelTask.class
>>>>    Last modified 2016-7-8; size 10220 bytes
>>>>    MD5 checksum f0262d363ad22b0e64e8e3e59d344cbc
>>>>    Compiled from "ScheduleTransferChannelTask.groovy"
>>>> Has anyone seen the same issue and share how to solve it?
>>>> Thanks~
>>>I think without looking at the actual bytecode there is no chance to
>>>tell what the problem is. "Illegal type in constant pool" is a very
>>>generic error, and it could mean anything from using the wrong invoke to
>>>a wrong ldc somewhere...
>>>bye Jochen
View raw message