[Pharo-project] 12186 image quit problem

Schwab,Wilhelm K bschwab at anest.ufl.edu
Fri Oct 8 12:41:40 EDT 2010

Not sure I follow.  Is this saying that one chooses between the default console output and printAllStacks(), or is it making printAllStacks() happen in response to the signal and leaving the usual output in place too?  I guess another option might be that all stacks get printed instead of just the active process??

From: pharo-project-bounces at lists.gforge.inria.fr [pharo-project-bounces at lists.gforge.inria.fr] On Behalf Of Levente Uzonyi [leves at elte.hu]
Sent: Friday, October 08, 2010 12:12 PM
To: Pharo-project at lists.gforge.inria.fr
Subject: Re: [Pharo-project] 12186 image quit problem

On Fri, 8 Oct 2010, Alexander Lazarević wrote:

> 2010/10/8 Levente Uzonyi <leves at elte.hu>:
>> On un*x you can send SIGUSR1 to the process of the VM to make it print all
>> stacks. IIRC Cog uses this signal for another purpose, so it doesn't work
>> with Cog.
> I think it's like that: On a vanilla/standard unix vm SIGUSR1 just
> terminates the vm. With a cog vm you trigger a printAllStacks with
> that Signal.
> http://lists.squeakfoundation.org/pipermail/squeak-dev/2010-July/152001.html

Indeed. Thanks for clarifying.


> Alex
> _______________________________________________
> Pharo-project mailing list
> Pharo-project at lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

More information about the Pharo-dev mailing list