>Was cysignals compiled with PARI support? Can you provide the cysignals >build log?
It was not and I think that fixed the problem! At least I couldn't reproduce it yet (not reliably reproducible bugs are annoying). I mainly looked into recent dependency changes for potential causes, although in retrospect it should have been obvious to look for differences to the cysignals spkg. Now I don't know why that ever worked... Anyawys, thanks. If that bug doesn't reappear, you saved me a lot of time. >But it might be something similar to this: >https://trac.sagemath.org/ticket/24986, >Not the same, but still a case of a signal being handled at some point >that causes some memory assignment to go awry and data structures to >be corrupted. Just as shot in the dark though. Thanks for the pointer. If it turns out the cysignals build didn't fix it after all I'll take a closer look at that. -- 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.
