Erratum: I think it did fix the bug, I just misunderstood a different error. Is this modification of coops config viable for upstream or should I find a way to grant thread safety in my own code ?
On Wed, Aug 28, 2019 at 6:17 PM Théo Cavignac <[email protected]> wrote: > Unfortunatly it did not fixed the bug to add -disable-interrupts. I still > have this class of bug spawning here and there with different instances and > different slots. > > Is there a way I could protect slot access from race conditions directly > in my code so that I identify the bug ? > > On 28/08/2019 16:46, [email protected] wrote: > > This is just a guess, but I think it just may be the case you are using the > slot before it has been initialized (see build-cache in coops.scm). > > After poking a bit, there seems indeed be a thread-safety issue when > lookup up object slots, I'm not sure if this is the case here. > > > I don't think the slots are uninitialized because sometimes the slot > used instead of another contains class instance. Still I would like to > try but I am not sure how to proceed to inject options in building > coops. Is it something like this : > CSC_OPTIONS='-disable-interrupts' chicken-install coops > > The easiest solution is to "chicken-install -r coops", cd to coops, > and add (csc-options "-disable-interrupts") to the "coops" extension > properties, then say "chicken-install" inside that directory. > > > felix > > >
_______________________________________________ Chicken-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/chicken-users
