From: "François Bissey" <f.r.bissey@massey.ac.nz>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] notebook backtrace
Date: Sat, 1 May 2010 10:15:49 +1200 [thread overview]
Message-ID: <201005011015.49522.f.r.bissey@massey.ac.nz> (raw)
In-Reply-To: <1272664373.5944.2@ledaig>
> Apparently in masking sage-4.4 to revert to 4.3.5 I had neglected to
> mask sage-doc-4.4. I had the wrong sage-doc installed for the test! In
> reverting to 4.3.5 other test failures were due to scipy as you
> indicate and others were due to matplotlib. I now have been able to
> reproduce test results I had previously for 4.3.5. Upon then upgrading
> to 4.4 I have many failures of the "type" indicated in the first post
> of this thread; i.e. of the "type"
>
> *** glibc detected *** /usr/bin/python2.6: corrupted double-linked list:
>
> with an associated backtrace and memory dump. I suppose Christopher
> will observe the same on his amd64.
For the record on x86 I have a number of tests failing due to
maxima-5.21.1/ecls-10.4. Hopefully those will go away in sage-4.4.1.
Most of the other failures are old.
I do not have anything like you do. What is worrying is I am guessing you
don't see any patterns in the failures. If it is all over the place I would
have a serious look at sage-lib and sage-core.
Francois
next prev parent reply other threads:[~2010-04-30 22:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 15:27 [gentoo-science] notebook backtrace Steven Trogdon
2010-04-30 0:18 ` François Bissey
2010-04-30 0:59 ` Steven Trogdon
2010-04-30 1:09 ` François Bissey
2010-04-30 1:13 ` Steven Trogdon
2010-04-30 1:54 ` François Bissey
2010-04-30 21:52 ` Steven Trogdon
2010-04-30 22:15 ` François Bissey [this message]
2010-04-30 22:30 ` Steven Trogdon
2010-04-30 22:47 ` François Bissey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201005011015.49522.f.r.bissey@massey.ac.nz \
--to=f.r.bissey@massey.ac.nz \
--cc=gentoo-science@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox