OK, let's try to do some tracing again: enable only the
"contentProvider " trace and re-post it.
Gabriel Petrovay wrote:
Dear Pawel,
I am only having an array of frames I instantiate once the getTopFrame
is requested. From that moment on I still send that same array.
For the second question, I do not override the equals. But
I guess that is an optimization issue for the UI and I am already
sending the same array. But I am actually sending 4 frames not only one.
If you were overriding equals it could be part of the problem.
-Pawel
Hmmm.....
On Thu, May 22, 2008 at 5:16 PM, Gabriel
Petrovay < gabipetrovay@xxxxxxxxx>
wrote:
Hi
guys,
I am building a debugger for a plugin and I have a problem with the
Debug View when I break a process and I display the stack frames. Once I
retrieve the stack frames of a thread the Debug View enters in an
infinite loop and continuously selects one frame at a time.
For example, if the Debug View displays the following tree:
Target
Thread
Frame1
Frame2
Frame3
Frame4
the there is a Job("children update") that is created in an infinite
loop and each execution of this job alternatively selects one of the
last two frames: Frame4, Frame3, Frame4, Frame3, ......
What am I doing wrong? For now I am just sending a dumb list of 4 frames
which is cached so the frames are the same after the first call.
Thanks!
--
MSc Gabriel Petrovay
MCSA, MCDBA, MCAD
Mobile: +41(0)787978034
_______________________________________________
platform-debug-dev mailing list
platform-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-debug-dev
|
