How do I debug an arbitrary Process? Help!
Ned Konz
ned at bike-nomad.com
Wed Feb 13 19:12:37 UTC 2002
On Wednesday 13 February 2002 09:52 am, Lex Spoon wrote:
> Hmm, maybe it has to do with the process gets suspended while Morphic is
> in different parts of an interaction cycle, and with your hack it tends
> to get suspended between cycles? If this is the case, a "yield" would
> probably be just as effective as a 200 millisecond delay. Neither is
> guaranteed to work, either, if this is the problem,
Actually, "self suspend" also works. Apparently the debugger wants a really
suspended context.
> Overall, I don't think there is a great solution. Interrupting
> processes at arbitrary times causes trouble. It seems like every thread
> library has "suspend" and "kill" in it to start with, followed a year or
> two later by these operations being deprecated. But, watchya gonna do?
My favorite method is VW's interruptWith: aBlock that allows you to do (for
instance):
someProcess interruptWith: [ self halt ].
--
Ned Konz
currently: Stanwood, WA
email: ned at bike-nomad.com
homepage: http://bike-nomad.com
More information about the Squeak-dev
mailing list
|