On Wednesday 23 March 2005 2:23 am, Cees de Groot wrote:
> And to add to the confusion, when the Linux images hangs it jumps to 99%
> CPU time.
>
> (I want a post-mortem image debugger ;))

What I do is this to figure out where a hung or unresponsive squeak is:

gdb -p <processid>

then:

# show current stack to stderr (my script that starts squeak directs stderr to 
uniquely named files)
call printCallStack()
# show all stacks:
call printAllStacks()
# flush output
call fflush(stderr)
# quit
q

-- 
Ned Konz
http://bike-nomad.com/squeak/