[Soot-list] Exception in transformation

Zeinab Lashkaripour lashkaripour at yahoo.com
Mon May 27 08:57:34 EDT 2013


sorry but, 
I sent the body with the wrong method name and parameters (although I think it might not be so important but I corrected it)


Regards


________________________________
 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: Monday, May 27, 2013 5:07 PM
Subject: Re: [Soot-list] Exception in transformation
 


Hi,

Thank you very much for replying Quentin.

> Try to compile the analyzed bytecode with the -g option to include debug info.
As I understand you mean after getting the Jimple, I should convert it to bytecode then use -g option?


> Can you find-out which method is problematic in class.jimple and output every Unit in the associated Body ? So that we can examinate the code.
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?
If the above is not correct then there might be some side effects due to the transformations that I'm making?
Please correct be Quentin.

Regards,
Zeinab


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

Hi,

On 05/26/2013 03:08 PM, Zeinab Lashkaripour wrote:
> Although I have used the command to give me the original variable names
> but the chain that I have does not contain the original names. Is there
> some thing that I have missed?

Try to compile the analyzed bytecode with the -g option to include debug 
info.

> On the other hand I get the exception below while the
 transformations
> are getting written. It should be mentioned that when I checked
> "class.jimple" the last part that was written inside code was related to
> a method that I have not transformed it therefore its odd!!
> (If this exception happened in one of the methods that I have
> transformed I would know what to do but, in this case I don't)

The exception you get usually appears because an IdentityStmt is located 
after a non-IdentityStmt in the method body. All the IdentityStmt should 
be packed at the beginning of the body.
Can you find-out which method is problematic in class.jimple and output 
every Unit in the associated Body ? So that we can examinate the code.

Regards.


-- 
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/20130527/3f738fa1/attachment-0001.html 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Method_Body.txt
Url: http://mailman.cs.mcgill.ca/pipermail/soot-list/attachments/20130527/3f738fa1/attachment-0001.txt 


More information about the Soot-list mailing list