On 2017-09-07, Simon King <[email protected]> wrote: > I expected a crash when *not* using libgap_enter/exit. But actually I am > getting the crash when I *do* use it. I see the message > sig_error() without sig_on() > followed by a loooong gdb backtrace. > > So, does one need sig_on()/sig_off() in addition to libgap_enter/exit?
Any idea? When I do libgap_enter() and then cdef GapElement_FiniteField zero = libgap(F.zero()) (where F=GF(2)), I get a crash. I am about to test whether I can make up a minimal example from it. When I first do cdef GapElement_FiniteField zero = libgap(F.zero()) and then libgap_enter(), a call to make_GapElement_FiniteField (copied from sage.libs.gap.element) crashes. If I do libgap_exit() before calling make_GapElement_FiniteField, it works again. And what about the "sig_error() without sig_on()"? I thought sig_on() is only possible if no Python calls happen. Thus, sig_on() is no option in my case. Best regards, Simon -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
