If you set Preferences logDebuggerStackToFile to false, do things work 
ok after that?


On 12/5/12 2:46 PM, Chris Muller wrote:
> Printing this before pressing Command+d on the Process browser:
>
>    Link allSubInstances count: [ : e | e nextLink==e]
>
> reports 0.
>
> AFTER I press Command+d, I have to press Command+. to interrupt the
> infinite recursion, which exposes the debugger which is trying to open
> the debugger on the process I selected (see below for the stack).  NOW
>
>    Link allSubInstances count: [ : e | e nextLink==e]
>
> reports 1, and the one instance is the Process I was trying to debug.
>
> So, I overrode Process>>#nextLink: setter to guard against setting it
> to himself and repeating the test.  The guard was never hit, but the
> same condition ('nextLink' referring to itself) still formed.  This is
> impossible since that's the only writer of that variable unless the VM
> or other low-level mechanism is setting the Process' nextLink.
>
> ================
> Here's the stack of trying to invoke 'debug' from the Process Browser.
>   A MethodContext is just trying to render its printString as part of
> Debugger operations but it can't because of the cycle.  Any ideas?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20121205/b83abd7f/attachment.htm