I'm mainly curious how it's possible that everything looks completely
normal in javap (checked a dozen times), but the class verifier complains
anyway? Something has to be different. Is there a way to dig deeper into a
class file?

Greetings

On Wed, 2 Feb 2022 at 23:14, Stefan Reich <
stefan.reich.maker.of....@googlemail.com> wrote:

> Hmm, no change with latest version.
>
> I did "git clone https://github.com/apache/commons-bcel.git"; and "mvn
> package".
>
> stefan@lenovo-ThinkPad-X220:~/dev/classreftest$ javac -cp
> bcel-6.6.0-SNAPSHOT.jar MakeBadClassFile.java
> stefan@lenovo-ThinkPad-X220:~/dev/classreftest$ java -cp
> bcel-6.6.0-SNAPSHOT.jar:. MakeBadClassFile
> Now please try: java BadClassFile
> stefan@lenovo-ThinkPad-X220:~/dev/classreftest$ java BadClassFile
> Error: Unable to initialize main class BadClassFile
> Caused by: java.lang.VerifyError: (class: BadClassFile, method: main
> signature: ([Ljava/lang/String;)V) Illegal type in constant pool
> stefan@lenovo-ThinkPad-X220:~/dev/classreftest$
>
> On Wed, 2 Feb 2022 at 22:59, Gary Gregory <garydgreg...@gmail.com> wrote:
>
>> You should try the latest from git master.
>>
>> Gary
>>
>> On Wed, Feb 2, 2022, 15:41 Stefan Reich
>> <stefan.reich.maker.of....@googlemail.com.invalid> wrote:
>>
>> > Hi again,
>> >
>> > actual problem this time...
>> >
>> > I think I am doing everything right... Decompilation in javap -v looks
>> > just like it should. But I get a VerifyError... I'm using JDK 17. Full
>> > program attached. Please advice, thank you :)
>> >
>> > # javac -cp bcel-6.5.0.jar MakeBadClassFile.java
>> > # java -cp bcel-6.5.0.jar:. MakeBadClassFile
>> > # java BadClassFile
>> > Error: Unable to initialize main class BadClassFile
>> > Caused by: java.lang.VerifyError: (class: BadClassFile, method: main
>> > signature: ([Ljava/lang/String;)V) Illegal type in constant pool
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> > For additional commands, e-mail: dev-h...@commons.apache.org
>>
>
>

Reply via email to