[Soot-list] Invalid bytecode after processing with soot (java.lang.VerifyError for invokespecial)

[Eric Bodden]

Hi Christina.

Apparently, the code you generate is incorrect. There could be 1000
reasons for this and it is impossible to tell without knowing the
generated code.

Did you try the -validate flag to Soot?
Another good idea is to generate Jimple and/or jasmin versions using
the "-f J" or "-f jasmin" flags. If you send us such versions of your
FMTest class then maybe we can help.

Eric

On 24 February 2012 13:36, Cristina Ilie <crysgirlro at yahoo.com> wrote:
> Hello,
>
> My tool (which uses Soot) has a problem with source files which contain
> "special invokes" when I'm generating .class.
> When I set the output to Dava type all is ok. My output source file works
> fine. But when I apply my tool to the same
> code example and I set the output as .class file I have the following
> problem: [1]. This is obvious that is from the
> special invoke call... I tried to take a look to the bytecode but I can't
> figure out... I read on some forums that similar
> problems were encountered when some optimizations tools made some
> annotations to the code and altered the
> bytecode making it invalid. I suppose here it's something similar... What to
> disable from soot to be sure that the bytecode
> is not altered? Or do you think the problem is elsewhere?
>
> [1] Exception in thread "main" java.lang.VerifyError: (class: AppSource,
> method: g_compute signature: (LDerivType;)LDerivType;)
> Incompatible object argument for invokespecial at
> FMTest.main(FMTest.java:23)
>
> Cristina
>
> _______________________________________________
> Soot-list mailing list
> Soot-list at sable.mcgill.ca
> http://mailman.cs.mcgill.ca/mailman/listinfo/soot-list
>



-- 
Eric Bodden, Ph.D., http://bodden.de/
Head of Secure Software Engineering Group at EC SPRIDE
Principal Investigator in Secure Services at CASED
Tel: +49 6151 16-75422    Fax: +49 6151 16-72051
Room 3.2.14, Mornewegstr. 30, 64293 Darmstadt