[erlang-bugs] NIF segfault when using dirty schedulers

[Steve Vinoski]

On Thu, Jan 21, 2016 at 12:26 AM, Paul Davis <paul.joseph.davis@REDACTED>
wrote:

> Hey all,
>
> I've recently run into a segfault while working with dirty schedulers.
> I managed to make a fairly concise reproducing test case at [1]. I
> included a stack trace at [2] from when the segfault occurs. This is
> definitely a racey segfault as well. I sometimes have to run `rebar
> eunit` a handful of times to trigger it.
>
> I'm not hugely familiar with all of the VM internals so I'm at a bit
> of a loss on where to start looking further. I did try and get rid of
> the requirement for eunit but I couldn't reproduce without it.
>
> This reproduces on both 17.5.6.4 where I found it and 18.2.2. I
> haven't tried master or anything of that nature.
>
> Let me know if there's anything else I can do to help debug this.
>
> Thanks,
> Paul
>
> [1] https://gist.github.com/davisp/1e71ec7f2f7a70d1b79c
> [2]
> https://gist.github.com/davisp/1e71ec7f2f7a70d1b79c#file-gdb_backtrace-txt


I'll have a look at your example, thanks for putting it together. Fro your
backtrace I'm guessing the issue is already fixed by available patches
which are not yet consolidated in any one branch or release.

--steve
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-bugs/attachments/20160121/82533d0c/attachment.htm>