| debugging plugins at runtime? [message #333642] |
Fri, 19 December 2008 08:45  |
Eclipse User |
|
|
|
Originally posted by: marc.esher.comcast.net
All,
I was wondering: is it possible to debug plugins at runtime; specifically,
plugins like Junit, Navigator, etc? The reason I ask is that I was checking
out Plugin Spy (alt-shift-F1) and thought it'd be sweet if I could, say, pop
up the resource navigator's code via the spy, set a breakpoint, and then
have those breakpoints catch so I can see what's going on under the hood.
Thinking out loud here... Thanks for ideas.
marc
|
|
|
| Re: debugging plugins at runtime? [message #333646 is a reply to message #333642] |
Fri, 19 December 2008 10:46  |
| Eclipse User |
|
|
|
Originally posted by: marc.esher.comcast.net
to clarify: I know I can achieve this by setting the breakpoint on the code
in the initial eclipse instance while launching a debug instance. That's not
what I'm talking about. Basically it seems to me that it'd be really handy
to be able to set the breakpoints from the plugin spy without having to
navigate through the "plugin references" tree looking for specific classes.
So.... I'm wondering if there's a convenience feature for doing so.
thanks.
"Marc E" <marc.esher@comcast.net> wrote in message
news:gig8hc$frh$1@build.eclipse.org...
> All,
> I was wondering: is it possible to debug plugins at runtime;
> specifically, plugins like Junit, Navigator, etc? The reason I ask is that
> I was checking out Plugin Spy (alt-shift-F1) and thought it'd be sweet if
> I could, say, pop up the resource navigator's code via the spy, set a
> breakpoint, and then have those breakpoints catch so I can see what's
> going on under the hood.
>
> Thinking out loud here... Thanks for ideas.
>
> marc
|
|
|
Powered by
FUDForum. Page generated in 0.03377 seconds
Home