[Soot-list] Paddle: call graph is incomplete

[Eric Bodden]

Hi Jochen.

Yes, Paddle currently has no direct support for TamiFlex.

However, since our first TechReport, we have implemented another
TamiFlex component, the "Booster". It is available on the TamiFlex
website and described in our upcoming ICSE Paper. The Booster takes
your program with reflection in it as input, along with the log file
that TamiFlex produced. As output, it produces a version where all the
logged reflective calls have been (sort of) replaced by normal method
calls. (It's actually a little more complex than that.) This
"de-reflectionized program" you could then pass to paddle, or to any
other static analysis tool too, as a matter of fact.

Eric

On 1 March 2011 18:35, Jochen Huck <jochen.huck at student.kit.edu> wrote:
> Hi,
> I use tamiflex to deal with reflection. When using SPARK, the call graph
> seems to be complete. When using Paddle it misses some edges. -p cg
> reflection-log:... seems to be independent of the actual call graph
> generation framework.
> Is it possible that Paddle doesn't recognize the reflection calls?
>
> Thanks, Jochen
> _______________________________________________
> Soot-list mailing list
> Soot-list at sable.mcgill.ca
> http://mailman.cs.mcgill.ca/mailman/listinfo/soot-list
>



-- 
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