On Thu, Jul 28, 2016 at 4:32 PM, Erik Bray <erik.m.b...@gmail.com> wrote: > ...and in particular, are any omalloc experts watching this list? > > I ask because my current issue in the Cygwin port of Sage is a > segfault that's occurring in Singular during a routine memory > deallocation of GMP integers. > > I'm working on getting a Singular compiled without omalloc to see if > that makes any difference. In the meantime I just thought I'd reach > out to see what expertise I have to draw on in the community.
Thanks everyone for all the tips. I'm heading out for vacation again but will be back in a week and will go through them one by one. For what it's worth I think I'm close in on the problem: The way Singular is being built and/or how DLLs are being loaded it's ending up with both GMP and MPIR simultaneously, and this causes a great deal of confusion, not the least of which that mp_set_memory_functions is being called in one but not the other. The end result is a segfault on a memory address that was allocated with the system allocator, but is being freed by omalloc. Not sure why this is happening but it must be a build issue. -- 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.
