Hi Machael, You wrote: > > > On Oct 29, 9:18 pm, Jaap Spies <[EMAIL PROTECTED]> wrote: >> Michael, >> > > Hello Jaap, > >> Remembering that dance(10) has a segmentation fault long before >> there was a function _choose, is it possible that some other >> part of the code is going wild? >> > > Sure, but so far no lead. Which specific version did exhibit that > behavior? I can build older releases locally and see if I can come up > with anything. >
On 23 Oct I wrote: To day I got with sage-2.8.8.1: > > sage: time dance(10) > > > > > > ------------------------------------------------------------ > > Unhandled SIGSEGV: A segmentation fault occured in SAGE. > > This probably occured because a *compiled* component > > of SAGE has a bug in it (typically accessing invalid memory) > > or is not properly wrapped with _sig_on, _sig_off. > > You might want to run SAGE under gdb with 'sage -gdb' to debug this. > > SAGE will now terminate (sorry). > > ------------------------------------------------------------ > Now that 2.8.10 with all your speed improvements is out I will do some > more testing with that release on sage.math with a 32 bit binary to > see if I can flush anything out with that. > Warning: see the reopened trac #217, I stupid changed some Py_ssize_t in ints, but knowing the nrows and ncols are small, there will be no problem, I hope! > As I wrote above: The issues with the refcount going insane is a nice > result from the debugging and that will hopefully lead to some > improvements in our fight against memleaks. > Thanks and good luck, Jaap --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
