[prev in list] [next in list] [prev in thread] [next in thread] 

List:       soot-list
Subject:    Re: [Soot-list] about the CFG of Jimple code
From:       Marc-Andre Laverdiere-Papineau <marc-andre.laverdiere-papineau () polymtl ! ca>
Date:       2013-03-25 11:13:22
Message-ID: 51503152.9060602 () polymtl ! ca
[Download RAW message or body]

Hi,

Jimple is designed to be more or less like bytecode. I'd be tempted to =

nickname it 'readable bytecode'

In some ways, some of the nice Java-level stuff like loops becomes =

desugared to gotos and labels, which is a lot less fun.

I think that the Soot APIs have some decent options for control flow =

stuff. If you examine the Units of a method body, I think you will get =

the information you need.

Marc-Andr=E9 Laverdi=E8re-Papineau
Doctorant - PhD Candidate

On 13-03-23 11:55 PM, Zhang Yufeng wrote:
> Hi all,
> Does the CFG from Jimple have the same structure as that from bytecode?
> In my project, after I get a log of a path in the bytecode(consisting of
> a sequence of log of yes\no on branches),
> I want to retrive the path on the CFG.
> So the structure of the CFG is important to me.
> I have tried several examples, and find that the structure is the same
> as that in the bytecode.
> But I am still not sure about this.
> Is there anybody know this?
> Thank you.
> Yufeng
>
>
> _______________________________________________
> Soot-list mailing list
> Soot-list@sable.mcgill.ca
> http://mailman.cs.mcgill.ca/mailman/listinfo/soot-list
>
_______________________________________________
Soot-list mailing list
Soot-list@sable.mcgill.ca
http://mailman.cs.mcgill.ca/mailman/listinfo/soot-list
[prev in list] [next in list] [prev in thread] [next in thread]