| Custom debug variables view [message #1066794] |
Thu, 04 July 2013 08:05  |
Eclipse User |
|
|
|
Is it possible somehow to extend the list of variables that are present in the Variables View when the program execution stops at a breakpoint?
Actually I would like to create an own view where I can display the contents of given class instances.
Just to image the way I figured out how to develop something like this:
-My host eclipse (1) is given with a set of plugins which constitue my "product". Part of this product is this debug view, which can be used
naturally one level above this host Eclipse.
-First runtime Eclipse (2), where the view is present.
-Second runtime (started from 2), where I actually want to do something with my product (this is Eclipse instance 3).
In order to be able to use my product, the codebase should be present in the launch configuration of 3 (either by passing the plugins from the
launch config of 2, or the product is entirely present again in the workspace of 2)
If the view is fully developed I will reduce this whole stuff to only 2 levels, because the product will be installed into the host.
From this point this whole thing will look like an ordinary debugging within Eclipse.
I am using the JDI Debug plugins and targets. I was able to create a breakpoint listener and
- Instance 1 is notified when instance 2 stops at a breakpoint. Here I am able to retrieve the StackFrames
- As I saw the interpretation and debugging is done by an external perl program. Does this one provide the StackFrames and their contents?
- Theoretically, what is the ClassLoader - JDIDebugTarget relationship?
- The Class instances I can observe from Instance 1 are not the ones which I want to see, because those come from Instance 3,
but I need to access them at the lowest level because those plugins can contribute to the view in Instance 2.
|
|
|
|
| Re: Custom debug variables view [message #1073250 is a reply to message #1067221] |
Wed, 24 July 2013 07:50  |
| Eclipse User |
|
|
|
|
Thanks for the reply and sorry for the huge delay, but I just had the time to look into the code you mentioned. It would be great if you could give me some more hints regarding the code. I saw that you have some listeners for certain kind of breakpoints and retrieve the "this" reference from the JDIThread when the execution stops at a constructor (TeamInstance). Do you just collect these references and display them in the view?
|
|
|
Powered by
FUDForum. Page generated in 0.03627 seconds
Home