Hi!
On 2017-09-07, Simon King <simon.k...@uni-jena.de> wrote:
> On 2017-09-07, Volker Braun <vbraun.n...@gmail.com> wrote:
>> Second question: Move the libgap_enter/exit outside of the loop, assuming
>> that the python functions don't themselves call libgap. If they do, you
>> will get a "RuntimeError: Entered a critical block twice". In that case,
>> move the libgap_enter/exit into the loop as far as necessary to have
>> non-overlapping libgap_enter/exit blocks.
>
> Since GapElement_List.__getitem__ (and the functions called by it) doesn't
> seem to use it, it will probably be fine (couldn't test it yet, though).
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?
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 sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
