[Glass] Cannot stop Seaside gems anymore

[Dale Henrichs via Glass]

Mariano,

`kill` works in 10.10.5 (Yosemite) for my Mac ...

Let's try to get a c stack trace. You'll need gdb installed (These are 
the instructions for installing Yosemite[1] and should be similar, but 
you probably need to check). ONce you're able to use gdb then you want 
to attach to your process using root:

     sudo /usr/local/bin/gdb

Then at the prompt:

     attach <pid>
     set confirm off
     set pagination off
     set backtrace limit 0
     thread apply all backtrace

And send the resulting trace ... in the mean time, `kill -9` should be 
okay to use on topaz or a gem.

Dale

[1] http://www.patosai.com/blog/post/installing-gdb-on-mac-os-x-yosemite
On 12/21/15 11:49 AM, Mariano Martinez Peck via Glass wrote:
> Hi guys,
>
> I am running in OSX. In the last weeks, I have re-setup a bit my 
> "linux" stack of tools in my OS (zsh, prezto, tmux, etc etc etc). I 
> have also updated to the very last updates from OSX. I am now in OSX 
> 10.11.2. GemStone is 3.2.9.
>
> Today I was doing something with my local GemStone and I found out I 
> cannot stop seaside gems again. I don't know if this could be related 
> or not to all the changes I been doing recently, but it looks weird.
>
> Whenever I try to stop my seaside gems (which simply do a "kill $pid 
> "), my gems processes are NOT killed and in the log I get this:
>
> *GemStone signal handler: signal 15 (SIGTERM), received from process 
> 14563 userId 501*
> * si_code: 0 at 1450726718, unknown SI_*
>
> Any clues? I have none at all...
>
> 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/20151221/80da2cf6/attachment.html>