Poking around a little bit I see an oddity I don't immediately 
understand. If I do:

[(Delay forSeconds: 100) wait] forkAt: 30

and debug from the ProcessBrowser, the debugger is looking at the call 
stack from my snippet.

If I do:

[(Delay forSeconds: 100) wait] forkAt: 50

then use the ProcessBrowser to debug it, the debugger is always in 
Process>>terminate

I don't imagine this is expected behavior.

Cheers,
Bob

On 12/5/12 3:55 PM, Bert Freudenberg wrote:
> On 2012-12-05, at 21:49, Bob Arning <arning315 at comcast.net> wrote:
>
>> Well, it will happen if you add something to a list that's already there. Try this:
>>
>> | list link |
>> list := LinkedList new.
>> link := Link new.
>> list add: link.
>> list add: link.
>> link explore.
>>
>> So if you send #resume to a process with priority less than the active process, it might happen. Or if you try to suspend the active process, but it's already on a suspended list.
>>
>> Cheers,
>> Bob
>>
>> On 12/5/12 3:19 PM, Chris Muller wrote:
>>> I hope someone in the VM community will weigh in; is it valid to
>>> create a cycle in the linked-list of one Process?
> Yes, it's certainly in the use of the primitive, not the primitive itself.
>
> Why does the process need to be resumed if it's going to be debugged anyway?
>
> - Bert -
>
>
>
>

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