[erlang-bugs] NIF segfault when using dirty schedulers

Paul Davis paul.joseph.davis@REDACTED
Thu Jan 21 06:26:33 CET 2016


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



More information about the erlang-bugs mailing list