[Soot-list] "Jimplification" time measurement

[Eric Bodden]

Hi again.

It sounds like you want to monitor the duration of calls to this method:

public interface MethodSource
{
    /** Returns a filled-out body for the given SootMethod. */
    public Body getBody(SootMethod m, String phaseName);
}

This interface has multiple implementations, depending on where Jimple
is produced from (.java files or .class files). It should be possible
to write, for instance, a small AspectJ aspect to do the
instrumentation.

Eric


2011/3/15 Társis Toledo <tarsiswt at gmail.com>:
> Yes I did. But it does not allow me to see how long it took for methods
> individually. It seems I will some to insert some kind callback mechanism
> into soot code in order to achieve my goal, which sounds inelegant and
> unpractical.
>
> Hopefully I'm wrong, but that may be the only way.
>
> Thank you for your time.
>
> Társis Wanderley Tolêdo
> Computer Science MSc. Candidade at Federal University of Pernambuco
>
>
>
> 2011/3/15 Eric Bodden <bodden at st.informatik.tu-darmstadt.de>
>>
>> Hi Társis.
>>
>> Before you try anything else, did you try the "-time" switch?
>>
>> Eric
>>
>> 2011/3/15 Társis Toledo <tarsiswt at gmail.com>:
>> > Hello everyone,
>> >
>> > I wish to measure the amount of time taken to "jimplify" methods
>> > individually of application classes. I have looked and don't think soot
>> > stores that kind of information. My question is: are there entry points
>> > in
>> > the code where I can encompass with calls like System.nanoTime()? If so,
>> > can
>> > I get some pointers to which class I should take a closer look?
>> >
>> > Thanks in advance.
>> >
>> > Társis Wanderley Tolêdo
>> > Computer Science MSc. Candidade at Federal University of Pernambuco
>> >
>> >
>> > _______________________________________________
>> > 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
>
>



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