[squeak-dev] Process-specific state difficult to debug...

Ben Coman btc at openInWorld.com
Thu Jan 29 15:57:41 UTC 2015

I don't know much about it, but I've been poking around there recently in
Pharo, so maybe I can l learn something more looking at this.  Can you be
specific about the specific variable you are referring to?  And can you
report a short script for others to test against to get to the point of
your question?

cheers -

On Thu, Jan 29, 2015 at 4:50 PM, Marcel Taeumel <
marcel.taeumel at student.hpi.uni-potsdam.de> wrote:

> Hi!
> There are process-specific variables. However, #doStep in Debugger does
> #completeStep: on the process object and Processor >> #activeProcess will
> be
> wrong during that execution.
> Is this a general problem of global state or could we fix that somehow?
> Best,
> Marcel
> --
> View this message in context:
> http://forum.world.st/Process-specific-state-difficult-to-debug-tp4802422.html
> Sent from the Squeak - Dev mailing list archive at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20150129/8bd4a699/attachment.htm

More information about the Squeak-dev mailing list