[Soot-list] SOLVED - Exception in transformation

[Zeinab Lashkaripour]

Hi,
Thank you very much Quentin.

I used the -g option first then ran my transformations and yes, all the variables had their original names.

Regards,
Zeinab



________________________________
 From: Zeinab Lashkaripour <lashkaripour at yahoo.com>
To: Quentin Sabah <quentin.sabah at inria.fr> 
Cc: "soot-list at sable.mcgill.ca" <soot-list at sable.mcgill.ca> 
Sent: Tuesday, May 28, 2013 12:06 AM
Subject: Re: [Soot-list] Exception in transformation
 


Hi again,


> No, I mean passing the -g option to javac when you compile the analyzed 
> program from .java to .class. This is only possible if you have the 
> sources of the classes you are analyzing.
If this is the solution then I do not know how to use -g option so that while performing the transformations I would be able to access the original names (because I need them while transforming). I think that the solution you gave is suitable if I wanted to inspect my code after the transformation, is this right?


Regards,
Zeinab



________________________________
 From: Quentin Sabah <quentin.sabah at inria.fr>
To: "soot-list at sable.mcgill.ca" <soot-list at sable.mcgill.ca> 
Sent: Monday, May 27, 2013 5:52 PM
Subject: Re: [Soot-list] Exception in transformation
 

> As I understand you mean after getting the Jimple, I should convert it
> to bytecode then use -g option?

No, I mean passing the -g option to javac when you compile the analyzed 
program from .java to .class. This is only possible if you have the 
sources of the classes you are analyzing.

> I'm not quite sure but, because the writing Jimple has stopped in the
> method that I have attached I think the problem is inside this method.

> Questions that I have are:
> If I'm not making a mistake this exception is not related to the
> transformation that I perform because if so I would have got an
 error
> before writing to the output (I mean while performing Transformation) Am
> I right?

The exception arise because the well-formedness of the body is checked 
before writing the output, I have no idea if this verification is also
performed earlier in Soot.

Before and after your analyzes, you should call the Body.validate() 
method on each transformed body, so you'll know if one of your
transformations is wrong.

You may also try to disable all your own transformations and analyzes. 
If the problem persists, then there might be a problem in Soot, 
otherwise it comes from your side.

-- 
Quentin Sabah, CIFRE Ph.D. student
Grenoble University
INRIA-SPADES                   | STMicroelectronics/AST
Montbonnot, France             | Grenoble, France
mailto:quentin.sabah at inria.fr  | mailto:quentin.sabah at st.com
phone: +33 476 61 54 57        | phone: +33 476 58 44 14
_______________________________________________
Soot-list mailing list
Soot-list at sable.mcgill.ca
http://mailman.cs.mcgill.ca/mailman/listinfo/soot-list



_______________________________________________
Soot-list mailing list
Soot-list at sable.mcgill.ca
http://mailman.cs.mcgill.ca/mailman/listinfo/soot-list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.cs.mcgill.ca/pipermail/soot-list/attachments/20130528/2cd719fa/attachment.html