On Sunday, December 30, 2012 5:40:05 PM UTC+1, Jean-Pierre Flori wrote: > > > I had good hopes that with a --without-pymalloc build, we'd catch a >> double free like this red handed, but no such luck (I cannot reproduce >> the problem at all on debug builds). > > Me neither, too bad. > At least it got us to have a working Python debug build. > And of course I cannot reproduce it on top of a usual build of sage-5.6.beta2. Even after playing with MALLOC_CHECK_.
On what kind of system did you perform your last tests? I feel kind of bored having to rebuild a previous beta once again and being even sure I'll get something to investigate. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
