[erlang-questions] How to diagnose stuck Erlang node

[Kirill Zaborsky]

Trying to fins any workaround to this "stuck node" scenario I've upgraded 
to R14B04 and turned on "heart".
But recently  the node once again stopped responding. And heart did not 
assume it to be stuck although I could not contact it.
I've tried to to get a crashdump with 'kill -USR1' but it appeared that 
once again crash dump was truncated. Does heart kills "dead" erlang node?
And the only thing that could be seen from the crash dump that the only 
running process was user_drv (just like in previous times) with program 
counter equal to "user_drv:server_loop/5 + 48". Is it possible to find out 
what exactly does it stands for?

P.S. It's quite strange to have a not much complex Erlang application with 
no way to find out what goes wrong or maybe I just don't see such ways?

Kind regards,
Kirill Zaborsky
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20111127/a1e61f0d/attachment.htm>