From: Christopher Schwan <cschwan@students.uni-mainz.de>
To: <gentoo-science@lists.gentoo.org>
Subject: Re: [gentoo-science] [sage-on-gentoo] Sage-4.5.3 segmentation fault
Date: Wed, 27 Oct 2010 10:07:25 +0200 [thread overview]
Message-ID: <201010271007.25794.cschwan@students.uni-mainz.de> (raw)
In-Reply-To: <20101026231412.291361f7.v_2e@ukr.net>
Hi,
On Tuesday 26 October 2010 22:14:12 v_2e@ukr.net wrote:
> On Wed, 27 Oct 2010 08:45:00 +1300
>
> François Bissey <f.r.bissey@massey.ac.nz> wrote:
> > I believe you may be the first person to try out python 2.6.6 with sage.
> > You may need to rebuild cython-0.12.1 (don't use 0.13) possibly numpy,
> > scipy, pexpect, ipython, matplotlib, mpmath, sympy, pynac, networx,
> > sphinx and then rebuild sage-clib and sage itself again. There may be
> > more but any one of these could be at fault.
>
> I have rebuilt Cython-0.12.1 today just before starting this thread.
> So, this is not because of Cython, I guess. I'll try to rebuild the
> packages you mentioned one by one and find the one causing the
> segfault. And then report back here.
If you do not find anything, please try the following:
USE=debug emerge -1 sage-baselayout
Also, make sure that the GNU Debugger is installed (emerge gdb). You may now
start Sage with
sage -gdb
which spawns Sage in a gdb session. Sage will crash just as before, but you
may retrieve a backtrace via typing
bt
That output would be interesting and may directly lead us to the root of the
problem.
>
> Regards,
> Vladimir
>
> -----
> <v_2e@ukr.net>
Cheers,
Christopher
next prev parent reply other threads:[~2010-10-27 8:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 9:32 [gentoo-science] [sage-on-gentoo] Sage-4.5.3 segmentation fault v_2e
2010-10-26 9:38 ` François Bissey
2010-10-26 18:53 ` v_2e
2010-10-26 19:45 ` François Bissey
2010-10-26 20:14 ` v_2e
2010-10-27 8:07 ` Christopher Schwan [this message]
2010-10-27 21:34 ` v_2e
2010-10-27 22:08 ` François Bissey
2010-11-10 23:00 ` v_2e
2010-11-11 8:51 ` Christopher Schwan
2010-11-26 11:32 ` Jari_42
2010-11-29 10:43 ` Christopher Schwan
2010-12-01 10:14 ` v_2e
2010-12-01 10:29 ` Christopher Schwan
2010-10-26 9:45 ` Christopher Schwan
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=201010271007.25794.cschwan@students.uni-mainz.de \
--to=cschwan@students.uni-mainz.de \
--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