[erlang-questions] Beam.smp killed by Linux
Fri Nov 3 11:34:17 CET 2017
We do not use any NIF nor linked in driver.
But I agree R16B03-1 is quite old (porting our app now to 20.1).
I’ll try to change to a newer hardware if 20.1 will not solve the issue.
Typical errors include:
> * Bug in the VM
> * Hardware error, especially if running on older hardware
> * NIF has a bug
> * Linked in driver has a bug
> On Fri, Nov 3, 2017 at 9:42 AM Frank Muller <frank.muller.erl@REDACTED>
>> Thanks guys.
>> I’ll try to recompile with 20.1 + debug symbols on and I’ll leg you know.
>> On 2 November 2017 at 15:02, Luke Bakken <luke@REDACTED> wrote:
>>>> Tracking down the root cause of this requires building a VM with debug
>>>> symbols and getting a core file from the next crash.
>>> In case that's unpractical, objdump'ing the beam.smp binary and
>>> navigating to the location of the crash might also help if the misbehaving
>>> code is listed under a routine with a readable name and that name can be
>>> traced back to the ERTS C code.
>> erlang-questions mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions