[erlang-questions] hanging nodes

Lukas Larsson lukas@REDACTED
Wed Aug 20 15:08:55 CEST 2014

Hello Vlad,

This is most probably a windows only issue as the code in the stacktrace
runs through a lot of windows specific code. I guess the easiest way would
be if you are able to write a testcase that can reproduce the error so that
I can debug it here. If that is not possible, maybe you can attach to the
process and send me a windows "core file"?

To do this you have to install WinDbg[1] and then do "File->Attach to a
Process". After this you open the WinDbg console and type ".dump /ma
c:\beam.smp.dmp" and then upload that file on a server where I can download
it. Also I assume you have used one of the installers on erlang.org? Which
version of windows+Erlang/OTP are you using?


On Wed, Aug 20, 2014 at 11:18 AM, Vlad Dumitrescu <vladdu55@REDACTED>

> Some details: the beam process seems to have a thread that sits and does
> something. I don't know if the following example stack helps.
> best regards,
> Vlad
> wow64cpu.dll!TurboDispatchJumpAddressEnd+0x63b
> wow64.dll!Wow64SystemServiceEx+0x1ce
> wow64.dll!Wow64LdrpInitialize+0x42a
> ntdll.dll!RtlIsDosDeviceName_U+0x23a27
> ntdll.dll!LdrInitializeThunk+0xe
> kernel32.dll!SetEvent+0x2
> beam.smp.dll!fd_stop+0x4f
> beam.smp.dll!terminate_port+0x64
> beam.smp.dll!erts_deliver_port_exit+0x225
> beam.smp.dll!driver_failure_atom+0x93
> beam.smp.dll!ready_output+0xa9
> beam.smp.dll!erts_port_task_execute+0x28d
> beam.smp.dll!schedule+0xb24
> beam.smp.dll!_process_main+0x125
> ntdll.dll!RtlImageNtHeader+0x716
> beam.smp.dll!do_erts_alcu_free+0x5f
> beam.smp.dll!erts_alcu_free_thr_spec+0x58
> beam.smp.dll!thr_wrapper+0xa6
> kernel32.dll!BaseThreadInitThunk+0x12
> ntdll.dll!RtlInitializeExceptionChain+0x63
> ntdll.dll!RtlInitializeExceptionChain+0x36
> On Wed, Aug 20, 2014 at 10:26 AM, Vlad Dumitrescu <vladdu55@REDACTED>
> wrote:
>> Hi!
>> I have some nodes that don't want to terminate and that I can't connect
>> to. Most of the times the nodes unregister from epmd, but even when they
>> don't they still are inaccessible.
>> I was hoping that by connecting to the node I can see why it is hanging,
>> but I get the feeling that the hanging is not inside user code (because
>> epmd detects the socket being closed, so the shutdown process is started).
>> This is on Windows, but I have some reports for something that looks
>> similar from Linux too.
>> I'm not used to debugging this kind of situations, so I hope that someone
>> has some advice for me.
>> best regards,
>> Vlad
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20140820/116c24e4/attachment.htm>

More information about the erlang-questions mailing list