On Fri, Apr 30, 2010 at 9:39 PM, Mike Hansen wrote:
> On Fri, Apr 30, 2010 at 9:27 PM, Dima Pasechnik wrote:
>> Seems that this is connected to the reported
>> *** glibc detected *** python: corrupted double-linked list:
>> 0x6140b350 ***
>> troubles.
>
> My guess is that it is indeed
> h
On Fri, Apr 30, 2010 at 9:27 PM, Dima Pasechnik wrote:
> Seems that this is connected to the reported
> *** glibc detected *** python: corrupted double-linked list:
> 0x6140b350 ***
> troubles.
My guess is that it is indeed
http://trac.sagemath.org/sage_trac/ticket/8830 . You can try
ins
I've built sage-4.4.1.alpha2 on ia64 (Skynet's iras), with gcc-4.5.0,
to investigate recently made GAP patches.
It builds, but during the process, as well as during 'make test' I see
lots of
Unhandled SIGSEGV: A segmentation fault occure
