A few times lately I have noticed I can no longer open a debugger from the
Process browser (via Command+d).  As soon as I select it the image locks up.

If I break in with Command+. right away I was able to do some minimal
tracing.  It appears the Process instance I want to debug; his #nextLink is
himself. This results an endless recursion when his printing method simply
tries to ask his #size.

Incidentally, the Process I wanted to debug was simply waiting on a
Semaphore of a network Socket, not actually doing any processing when I
tried to debug it, and I can reproduce this problem every time.

I *know* I used to be able to debug these; anyone have any ideas what could
be wrong now?

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