[Soot-list] Soot enquiries

[Eric Bodden]

Hi Ikpeme.

You could use a combination of LocalMustAliasAnalysis or
LocalMustNotAliasAnalysis (depending on what you want) to check which
parameters are aliased with your variable. Then in a next step you
could use the call graph to determine all callers of your method. For
those call sites you then inspect the Locals passed to those calls.

Eric

On 14 February 2011 07:40, ikpeme <ikpeme at gatech.edu> wrote:
> Hi Eric,
>
> I was able to figure out my initial problem. I have another question for you. I am trying to do a whole program analysis and I have successfully created my callgraph. I will like to do a data flow analysis on a method to figure out the source of its parameter. For example, given a method M1 that calls another method M2 with parameters. How do I determine that source of the parameter (while in method M2) is some variable in M1. Can it be done with InfoFlowAnalysis and if so how?
>
> Ikpeme
>
>
>
> ----- Original Message -----
> From: "Eric Bodden" <bodden at st.informatik.tu-darmstadt.de>
> To: "ikpeme" <ikpeme at gatech.edu>
> Cc: soot-list at sable.mcgill.ca
> Sent: Wednesday, February 9, 2011 3:17:14 AM
> Subject: Re: Soot enquiries
>
> Hello.
>
>> Hi Eric
>
> There's certainly more people on this list willing to help you out.
>
>> Exception in thread "main" soot.AbstractSootMethodRef$ClassResolutionFailedException: Class java.lang.CharacterData doesn't have method of([int]) : java.lang.CharacterData; failed to resolve in superclasses and interfaces Looking in java.lang.CharacterData which has methods []
>
> Typically you get this exception when using an inconsistent set of
> class files, and because the Java runtime library is usually
> consistent with itself I have actually never seen this issue on a
> java.lang.* class.
>
> What happens when you type the following?
>
> javap -private -classpath <your rt.jar> java.lang.CharacterData
>
> You should be seeing the contents of java.lang.CharacterData. Does the
> method of([int]) show up?
>
> Eric
> --
> Dr. Eric Bodden, http://bodden.de/
> Principal Investigator in Secure Services at CASED
> Coordinator of the CASED Advisory Board of Study Affairs
> PostDoc at Software Technology Group, Technische Universität Darmstadt
> Tel: +49 6151 16-5478    Fax: +49 6151 16-5410
> Mailing Address: S2|02 A209, Hochschulstraße 10, 64289 Darmstadt
>



-- 
Dr. Eric Bodden, http://bodden.de/
Principal Investigator in Secure Services at CASED
Coordinator of the CASED Advisory Board of Study Affairs
PostDoc at Software Technology Group, Technische Universität Darmstadt
Tel: +49 6151 16-5478    Fax: +49 6151 16-5410
Mailing Address: S2|02 A209, Hochschulstraße 10, 64289 Darmstadt