| profile plugin [message #70762] |
Sat, 13 May 2006 18:22  |
Eclipse User |
|
|
|
Originally posted by: irbull.cs.uvic.ca
Hi All,
I am doing some testing for the Callisto release, and I thought I would
try my hand at TPTP. I have D/L the the latest (4.2 and all
dependencies). It seems to start fine and I can profile a simple Java
application. I then tried to profile an eclipse plugin. I wrote a
simple plugin, launched my runtime workbench, and it worked fine. I
then tried to profile my runtime workbench (profile as-> eclipse
application). The profiler seems ok, but my plugin isn't there.
Actually no plugins from my original workbench are there.
The profiler was launched with (All workspace and enabled external
plug-ins). (Same launch configuration I used to test my plugin).
Is this supposed to work, or is there something fundamental I am missing?
Cheers,
Ian
|
|
|
|
| Re: profile plugin [message #70781 is a reply to message #70770] |
Mon, 15 May 2006 15:03  |
| Eclipse User |
|
|
|
Originally posted by: nmehrega.ca.ibm.com
This is a multipart message in MIME format.
--=_alternative 0052BCA98525716F_=
Content-Type: text/plain; charset="US-ASCII"
Make sure you're not accidentally filtering out your plugins. In TPTP
4.1, go to your profile launch configuration: click on the profile button
-> select 'profile..' -> select your launch configuration -> click on the
profiling tab -> select your profiling set -> edit -> next -> select your
profiling option -> next -> check your filterset here and make sure you're
not accidentally filtering out your plugin. Note by default all classes
in the org* packages are filtered out.
Navid Mehregani
--=_alternative 0052BCA98525716F_=
Content-Type: text/html; charset="US-ASCII"
<br><font size=2 face="sans-serif">Make sure you're not accidentally filtering
out your plugins. In TPTP 4.1, go to your profile launch configuration:
click on the profile button -> select 'profile..' -> select your
launch configuration -> click on the profiling tab -> select your
profiling set -> edit -> next -> select your profiling option
-> next -> check your filterset here and make sure you're not accidentally
filtering out your plugin. Note by default all classes in the org*
packages are filtered out.</font>
<br>
<br><font size=2 face="sans-serif">Navid Mehregani</font>
--=_alternative 0052BCA98525716F_=--
|
|
|
| Re: profile plugin [message #70870 is a reply to message #70770] |
Mon, 15 May 2006 22:13 |
| Eclipse User |
|
|
|
Originally posted by: irbull.cs.uvic.ca
Thanks Ben, I had this problem too. Look at Navid's response, I was
filtering my code so nothing was bring recorded.
Cheers,
ian
Ben Xu wrote:
> I have this problem too.
> The plugin to be profiled just can't be seen int the profile tab.
> It seems that only some standard plugin can be profiled.
> BTW: Ian, what view can you see when you just profile these standard
> plugin.
> I see nothing but something like
> "no data is avaliable for display. The object selected in the profiling
> monitor views does not contain this type information."
> I selected the profile option and nothing change.
>
> I run TPTP4.1.0.1 on eclpse 3.1.2 on linux.
>
|
|
|
|
Powered by
FUDForum. Page generated in 0.02207 seconds
] 
Search
Help
Register
Login
Home
