[Glass] Kill gem but get stack?

Mariano Martinez Peck via Glass glass at lists.gemtalksystems.com
Tue Sep 20 05:50:44 PDT 2016

That was helpful!  Thank you very much Otto.
I didn't even tried as I thought it was something Pharo-specific. I am very
glad to see it works here too.
In fact, I think it's better as it doesn't kill the gem. In Pharo, as I
know, it kills and dumps the stack. I am not sure if you can dump the stack
without killing it.

Anyway, thanks for your help.

On Tue, Sep 20, 2016 at 9:38 AM, Otto Behrens <otto at finworks.biz> wrote:

> You can also send sigusr1 to a gem. It will dump the stack to the gem log.
> On 20 Sep 2016 2:34 PM, "Mariano Martinez Peck via Glass" <
> glass at lists.gemtalksystems.com> wrote:
>> Hi guys,
>> I have a background job which used to take an hour that is taking now....
>> more than a day. I am not sure if there is an endless loop or something
>> terrible slow.  If I kill the gem process, I get nothing written in the log
>> so I cannot know anything of what was that gem doing.
>> In Pharo, if I send SIGUSR1 to the VM for example, the VM is stopped and
>> the active/current Smalltalk stack is written in STDOUT. Is there something
>> like this in GemStone?
>> Or any other tool that help me know what the hell is happening with my
>> gem?
>> Thanks in advance
>> --
>> Mariano
>> http://marianopeck.wordpress.com
>> _______________________________________________
>> Glass mailing list
>> Glass at lists.gemtalksystems.com
>> http://lists.gemtalksystems.com/mailman/listinfo/glass

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20160920/94f23b88/attachment.html>

More information about the Glass mailing list