Gentoo Archives: gentoo-science

From: "François Bissey" <f.r.bissey@×××××××××.nz>
To: gentoo-science@l.g.o
Subject: Re: [gentoo-science] notebook backtrace
Date: Fri, 30 Apr 2010 22:16:03
Message-Id: 201005011015.49522.f.r.bissey@massey.ac.nz
In Reply to: Re: [gentoo-science] notebook backtrace by Steven Trogdon
1 > Apparently in masking sage-4.4 to revert to 4.3.5 I had neglected to
2 > mask sage-doc-4.4. I had the wrong sage-doc installed for the test! In
3 > reverting to 4.3.5 other test failures were due to scipy as you
4 > indicate and others were due to matplotlib. I now have been able to
5 > reproduce test results I had previously for 4.3.5. Upon then upgrading
6 > to 4.4 I have many failures of the "type" indicated in the first post
7 > of this thread; i.e. of the "type"
8 >
9 > *** glibc detected *** /usr/bin/python2.6: corrupted double-linked list:
10 >
11 > with an associated backtrace and memory dump. I suppose Christopher
12 > will observe the same on his amd64.
13 For the record on x86 I have a number of tests failing due to
14 maxima-5.21.1/ecls-10.4. Hopefully those will go away in sage-4.4.1.
15 Most of the other failures are old.
16 I do not have anything like you do. What is worrying is I am guessing you
17 don't see any patterns in the failures. If it is all over the place I would
18 have a serious look at sage-lib and sage-core.
19
20 Francois

Replies

Subject Author
Re: [gentoo-science] notebook backtrace Steven Trogdon <strogdon@×××××.edu>