Re: [sage-devel] Re: segfault (involving flint, libthread, randstate)

2017-05-11 Thread Jean-Pierre Flori
Here's the bt for the latter example: #0 visit_decref (op=0xfdc9906aac2f2efe, data=0x0) at Modules/gcmodule.c:360 #1 0x3fffad7f61e0 in __pyx_tp_traverse_4sage_4misc_9randstate_randstate ( o=0x3ffb1a37c5d0, v=@0x3fffb7f62aa8: 0x3fffb7eb91d0 , a=0x0) at

Re: [sage-devel] Re: segfault (involving flint, libthread, randstate)

2017-05-11 Thread Vincent Delecroix
I confused flint_rand_t and gmp_randstate_t. And our randstate does not support flint yet... I will postpone the changes to randomize to another ticket. Sorry for the noise. On 11/05/2017 11:55, Dima Pasechnik wrote: given libpthread being involved, I guess it might have to do with GIL vs

Re: [sage-devel] Re: segfault (involving flint, libthread, randstate)

2017-05-11 Thread Vincent Delecroix
The bug also shows up with {{{ sage: a = matrix(QQ, 1) sage: a.randomize() sage: del a sage: import gc sage: gc.collect() }}} On 11/05/2017 11:55, Dima Pasechnik wrote: given libpthread being involved, I guess it might have to do with GIL vs NOGIL stuff... On Thursday, May 11, 2017 at

[sage-devel] Re: segfault (involving flint, libthread, randstate)

2017-05-11 Thread Dima Pasechnik
given libpthread being involved, I guess it might have to do with GIL vs NOGIL stuff... On Thursday, May 11, 2017 at 10:50:39 AM UTC+1, vdelecroix wrote: > > Dear all, > > While working on [1] I stumbled on a strange segfault. Namely, with the > branch applied I got > > {{{ > sage: a =