| probekit question [message #133552] |
Wed, 30 July 2008 01:23  |
Eclipse User |
|
|
|
Originally posted by: ebraun.site.uottawa.ca
Hi,
I need to find out when a loop (for, while, etc..) are entered and exited.
Can I find out this information using one of the probekit Fragment types? I
have already got the method entry and exits printing.
Thanks,
eb
|
|
|
|
| Re: probekit question [message #133578 is a reply to message #133565] |
Wed, 30 July 2008 19:07  |
| Eclipse User |
|
|
|
Originally posted by: ebraun.site.uottawa.ca
Thanks Paul.
Is there any way of analysing the execution trace created via the probekit
to find loops etc? Using TPTP or anyother free tool.
Thanks,
eb
"Paul Slauenwhite" <paules@ca.ibm.com> wrote in message
news:g6ppg4$tge$1@build.eclipse.org...
> Hi eb,
> Method entry and exit is lowest level of granularity available.
>
> Paul
> "eb" <ebraun@site.uottawa.ca> wrote in message
> news:g6ofrj$51q$1@build.eclipse.org...
>> Hi,
>>
>> I need to find out when a loop (for, while, etc..) are entered and
>> exited. Can I find out this information using one of the probekit
>> Fragment types? I have already got the method entry and exits printing.
>>
>> Thanks,
>>
>> eb
>
>
|
|
|
|
| Re: probekit question [message #133629 is a reply to message #133591] |
Thu, 31 July 2008 17:54 |
| Eclipse User |
|
|
|
Originally posted by: ebraun.site.uottawa.ca
Thanks Paul, you saved me time with your answers.
I managed to generate a trace using the method level (entry/exit probes) I
can get execution trace for all my applications except for an eclipse
plug-in that I am testing. All I am doing is having the entry & exit of
methods printed on the consol and saving the consol to file. I can't see
why it does not work for plug-in, do you?
As for the loop detection a patter matching on the trace might be an easier
way to go since I really don't know the TPTP code.
Thanks,
eb
"Paul Slauenwhite" <paules@ca.ibm.com> wrote in message
news:g6semb$6cd$1@build.eclipse.org...
> Hi eb,
> Probekit does not generate a trace. The user-defined probes are weaved
> in the byte code (statically/dynamically) at various support fragment
> types (either callsite or method level). The user-defined probes may
> emit trace data but not Probekit. You would have to modify the TPTP code
> to provide a loop fragment type.
>
> Paul
> "eb" <ebraun@site.uottawa.ca> wrote in message
> news:g6qe6k$a41$1@build.eclipse.org...
>> Thanks Paul.
>>
>> Is there any way of analysing the execution trace created via the
>> probekit to find loops etc? Using TPTP or anyother free tool.
>>
>> Thanks,
>>
>> eb
>>
>> "Paul Slauenwhite" <paules@ca.ibm.com> wrote in message
>> news:g6ppg4$tge$1@build.eclipse.org...
>>> Hi eb,
>>> Method entry and exit is lowest level of granularity available.
>>>
>>> Paul
>>> "eb" <ebraun@site.uottawa.ca> wrote in message
>>> news:g6ofrj$51q$1@build.eclipse.org...
>>>> Hi,
>>>>
>>>> I need to find out when a loop (for, while, etc..) are entered and
>>>> exited. Can I find out this information using one of the probekit
>>>> Fragment types? I have already got the method entry and exits printing.
>>>>
>>>> Thanks,
>>>>
>>>> eb
>>>
>>>
>>
>
>
|
|
|
| Re: probekit question [message #133820 is a reply to message #133629] |
Wed, 06 August 2008 10:47 |
 Paul Slauenwhite
Messages: 975
Registered: July 2009 |
Senior Member |
|
|
Hi eb,
For your Eclipse plug-ins, make sure your probe classes or JAR are on
the plug-in's classpath.
Also, your probe could log the method entry/exit points to a Java
Logging logger, configured to write to a local file.
Paul
"eb" <ebraun@site.uottawa.ca> wrote in message
news:g6su95$ohu$1@build.eclipse.org...
> Thanks Paul, you saved me time with your answers.
>
> I managed to generate a trace using the method level (entry/exit probes) I
> can get execution trace for all my applications except for an eclipse
> plug-in that I am testing. All I am doing is having the entry & exit
> of methods printed on the consol and saving the consol to file. I can't
> see why it does not work for plug-in, do you?
>
> As for the loop detection a patter matching on the trace might be an
> easier way to go since I really don't know the TPTP code.
>
> Thanks,
>
> eb
>
>
> "Paul Slauenwhite" <paules@ca.ibm.com> wrote in message
> news:g6semb$6cd$1@build.eclipse.org...
>> Hi eb,
>> Probekit does not generate a trace. The user-defined probes are
>> weaved in the byte code (statically/dynamically) at various support
>> fragment types (either callsite or method level). The user-defined
>> probes may emit trace data but not Probekit. You would have to modify
>> the TPTP code to provide a loop fragment type.
>>
>> Paul
>> "eb" <ebraun@site.uottawa.ca> wrote in message
>> news:g6qe6k$a41$1@build.eclipse.org...
>>> Thanks Paul.
>>>
>>> Is there any way of analysing the execution trace created via the
>>> probekit to find loops etc? Using TPTP or anyother free tool.
>>>
>>> Thanks,
>>>
>>> eb
>>>
>>> "Paul Slauenwhite" <paules@ca.ibm.com> wrote in message
>>> news:g6ppg4$tge$1@build.eclipse.org...
>>>> Hi eb,
>>>> Method entry and exit is lowest level of granularity available.
>>>>
>>>> Paul
>>>> "eb" <ebraun@site.uottawa.ca> wrote in message
>>>> news:g6ofrj$51q$1@build.eclipse.org...
>>>>> Hi,
>>>>>
>>>>> I need to find out when a loop (for, while, etc..) are entered and
>>>>> exited. Can I find out this information using one of the probekit
>>>>> Fragment types? I have already got the method entry and exits
>>>>> printing.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> eb
>>>>
>>>>
>>>
>>
>>
>
|
|
|
Powered by
FUDForum. Page generated in 0.02235 seconds
] 
Search
Help
Register
Login
Home
