Re: Segfault by purging native and reloading beam

Forgot to include the crash information, but it looks like it's happening
far away from where the corruption occurred, so not that much help:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fe8d2b33700 (LWP 18980)]
process_main () at beam/beam_emu.c:2610
2610        result = (*bf)(c_p, reg, I);

#0  process_main () at beam/beam_emu.c:2610
#1  0x00000000004a8548 in sched_thread_func (vesdp=0x7f5b3b250380)
    at beam/erl_process.c:5281
#2  0x00000000005be5d0 in thr_wrapper (vtwd=0x7fff4cdbf930)
    at pthread/ethread.c:106
#3  0x00007f5b3b8f7e9a in start_thread ()
   from /lib/x86_64-linux-gnu/libpthread.so.0
#4  0x00007f5b3b41c8bd in clone () from /lib/x86_64-linux-gnu/libc.so.6
#5  0x0000000000000000 in ?? ()


        /Richard

On Fri, May 15, 2015 at 2:18 PM, Richard Carlsson <
[email protected]> wrote:

> This one was a bit tricky to minimize: you have to load beam code, then
> remove it fully, then load native, remove it fully again, then reload the
> beam code. Repeatable every time on plain old R15B03-1 and about one in
> three times on 18.0.  See example module.
>
>         /Richard
>

_______________________________________________
erlang-bugs mailing list
[email protected]
http://erlang.org/mailman/listinfo/erlang-bugs