New issue 2545: Segfault using futurist library
https://bitbucket.org/pypy/pypy/issues/2545/segfault-using-futurist-library
Mihnea Saracin:
Hello,
I`ve been using futurist library (using pip install futurist) and got the
following segfault. It uses threads and sometimes it crashes. To collect the
trace I have a pypy compiled with --lldebug –withmod-faulthandler
–withmod-_vmprof. My OS is Linux Mint 18.1 Serena with kernel 4.4.0-53 and GCC
5.4.0.
I've banged my head over this issue for some days now, and managed to reduce it
to a small Python script (attached to this issue), but I don't know how to
continue. Do you have any ideas on how can I approach this?
Thank you,
Mihnea
```
#!gdb
Program terminated with signal SIGABRT, Aborted.
#0 0x00007ffff2d27428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
54 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
[Current thread is 1 (Thread 0x7fffeefab700 (LWP 8816))]
(gdb) bt
#0 0x00007ffff2d27428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#1 0x00007ffff2d2902a in __GI_abort () at abort.c:89
#2 0x00007ffff60f4ae0 in RPyAssertFailed
(filename=filename@entry=0x7ffff6280951 "rpython_memory_gc.c",
lineno=lineno@entry=19121,
function=function@entry=0x7ffff6281880 <__FUNCTION__.403983>
"pypy_g_IncrementalMiniMarkGC_visit", msg=msg@entry=0x7ffff627f840 "pinned
object in 'objects_to_trace'") at support.c:20
#3 0x00007ffff5ccb267 in pypy_g_IncrementalMiniMarkGC_visit
(l_obj_79068=0x7fffe57e14e8, l_self_25111=0x7ffff69aee20
<pypy_g_rpython_memory_gc_incminimark_IncrementalMiniMar>) at
rpython_memory_gc.c:19121
#4 pypy_g_IncrementalMiniMarkGC_visit_all_objects_step
(l_self_25090=l_self_25090@entry=0x7ffff69aee20
<pypy_g_rpython_memory_gc_incminimark_IncrementalMiniMar>,
l_size_to_track_0=l_size_to_track_0@entry=94371840) at
rpython_memory_gc.c:16569
#5 0x00007ffff5cd2a39 in pypy_g_IncrementalMiniMarkGC_major_collection_step
(l_self_25077=l_self_25077@entry=0x7ffff69aee20
<pypy_g_rpython_memory_gc_incminimark_IncrementalMiniMar>,
l_reserving_size_3=l_reserving_size_3@entry=0) at rpython_memory_gc.c:15376
#6 0x00007ffff5cd391a in
pypy_g_IncrementalMiniMarkGC_minor_collection_with_majo
(l_self_25060=l_self_25060@entry=0x7ffff69aee20
<pypy_g_rpython_memory_gc_incminimark_IncrementalMiniMar>,
l_extrasize_1=l_extrasize_1@entry=0) at rpython_memory_gc.c:12227
#7 0x00007ffff5cd7c22 in
pypy_g_IncrementalMiniMarkGC_minor_collection_with_majo (l_extrasize_1=0,
l_self_25060=0x7ffff69aee20
<pypy_g_rpython_memory_gc_incminimark_IncrementalMiniMar>)
at rpython_memory_gc.c:7319
#8 pypy_g_IncrementalMiniMarkGC_collect_and_reserve
(l_self_25019=0x7ffff69aee20
<pypy_g_rpython_memory_gc_incminimark_IncrementalMiniMar>,
l_totalsize_25634=392) at rpython_memory_gc.c:7312
#9 0x00007ffff5cda3f4 in pypy_g_IncrementalMiniMarkGC_malloc_fixedsize
(l_self_25029=0x7ffff69aee20
<pypy_g_rpython_memory_gc_incminimark_IncrementalMiniMar>,
l_typeid_22=<optimized out>,
l_size_87=<optimized out>, l_needs_finalizer_1=<optimized out>,
l_is_finalizer_light_2=<optimized out>, l_contains_weakptr_2=<optimized out>)
at rpython_memory_gc.c:8441
#10 0x00007fffef6b9bf7 in ?? ()
#11 0x0000000000000000 in ?? ()
```
_______________________________________________
pypy-issue mailing list
pypy-issue@python.org
https://mail.python.org/mailman/listinfo/pypy-issue
