Re: erl_lock_count segfault
Lukas Larsson <[email protected]>
| Newsgroups | gmane.comp.lang.erlang.bugs |
|---|---|
| Message-ID | <[email protected]> |
Well, you can never be entierly sure, but it fails in this line[1] and I
don't really see that happening unless malloc returns NULL.
Do you still have the core file? Could you do a "bt full"+"info
registers"+"disassemble lcnt_thread_data_alloc" on the thread that fails?
Lukas
[1]:
https://github.com/erlang/otp/blob/bbfc75ea8795d26a2fe9254f3f646e761f2ad61e/erts/emulator/beam/erl_lock_count.c#L154
On 04/08/14 16:02, Louis-Philippe Gauthier wrote:
> Are you sure? This happens on a system with 30+ GB of free memory...
>
>
> On Mon, Aug 4, 2014 at 4:56 AM, Lukas Larsson <[email protected]
> <mailto:[email protected]>> wrote:
>
> Hello,
>
> This happens when malloc returns NULL. I'll add a check so that
> there is a nicer error message, but there is not much we can do
> when there is no memory left.
>
> Lukas
>
> On 25/07/14 17:49, Louis-Philippe Gauthier wrote:
>> Hi,
>> Looks like in some certain conditions I get a segfault when
>> starting the VM when compiled with lock counter.
>>
>> https://gist.github.com/lpgauth/27e66f7a2104d8b5af74
>>
>> LP
>>
>>
>> _______________________________________________
>> erlang-bugs mailing list
>> [email protected] <mailto:[email protected]>
>> http://erlang.org/mailman/listinfo/erlang-bugs
>
>
>
>
> _______________________________________________
> erlang-bugs mailing list
> [email protected]
> http://erlang.org/mailman/listinfo/erlang-bugs
_______________________________________________
erlang-bugs mailing list
[email protected]
http://erlang.org/mailman/listinfo/erlang-bugs