Troy Daniels <[EMAIL PROTECTED]> writes:
> Hello,
>
> There appears to be a bug in JDEbug regarding circular references. I was
> trying to look at a java.util.LinkedList. The implementation in my JDK uses a
> class like the following:
>
> class LLNode {
> Object element;
> LLNode next;
> LLNode previous;
> }
>
> where next and previous point to the next and previous elements of the list.
> Looking at the first element was fine. I clicked on the reference to the first
> LLNode, and expanded element. When I tried to look at the second element by
> expanding next, the mechanism to presever the expanded state imploded. It
> expanded the LLNode for next, then next.previous, then next.previous.next, and
> so on, looping between those two two objects until it hit some iteration limit.
>
> As a result, I couldn't look at any local variables. It apparently even failed
> to set up the properties so that I could close the objects. This persisted
> through exiting the debugger and starting a new run.
>
> In general, the mechanism is good and user full, but is there a way to turn if
> off in cases like this?
No. Fixing this has been in my todo for a while.
The mechanism caches the name of the variable, in order to know what to open.
This works for most cases, but there a few cases, like the linked list and the
detail cause within exceptions that causes the behavior.
The cache name should include the id of the object. That would avoid the
recursion.
If I get the chance I will try to patch this, before the next release.
Javier
>
> Troy
>
>
> Troy Daniels
> [EMAIL PROTECTED]
> 781-273-3388 x218
>
