public inbox for gentoo-science@lists.gentoo.org
 help / color / mirror / Atom feed
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: Mon, 29 Nov 2010 11:43:10 +0100	[thread overview]
Message-ID: <201011291143.10495.cschwan@students.uni-mainz.de> (raw)
In-Reply-To: <30308916.post@talk.nabble.com>

Hi,

On Friday 26 November 2010 12:32:35 Jari_42 wrote:
> Hi,
> 
> Just to report that I can reproduce this exact error on my amd64 gentoo
> install with Sage-4.6-r1 and python-2.6.6-r1.

Thanks for reporting! So it looks like this is not problem specific to just one 
computer - if there is anybody else who has the same problem, please write a 
mail to me (you do not need to mail to the list) and attach a file with the 
emerge --info output. I would also like to have emerge --info from Jari - 
hopefully I can find a difference to my system.

Unfortunately, I can not reproduce this error on amd64. This weekend I 
upgraded Sage in a prefixed environment to 4.6 but that went fine. After 
upgrading gcc to 4.5.1 I recompiled my entire prefix (emerge -e @world), but I 
still can not reproduce it.

For the time being, I can only recommend these general instructions:

1. make sure everything is up-to-date
2. make sure revdep-rebuild reports no package

If you have spare cpu time you may recompile world (this sounds really crazy, 
but I am running out of options ;) ) or at least Sage and it dependencies:

    emerge -C sage
    emerge --depclean -a
    emerge sage

This would make sure you do not have unintential old packages installed (this 
may have happened if I had done major changes to ebuilds without upgrading 
their revision number - this "should" not be the case, of course).

Christopher

> 
> Thanks,
> Jari
> 
> On Thursday 11 November 2010 00:00:20 v_2e@ukr.net wrote:
> >   Hello!
> > 
> > On Thu, 28 Oct 2010 11:08:28 +1300
> > 
> > François Bissey <f.r.bissey@massey.ac.nz> wrote:
> > > thanks for the debugging trace Vladimir.
> > > It looks like the problem is in pynac, it may be a compatibility
> > > problem with python 2.6.6. You have gone in uncharted territories
> > > with this version of python. Christopher knows more about pynac
> > > than me, he may be able to do something about it.
> > > 
> > > Thanks for the report.
> > > 
> > > Francois
> > > 
> >   I just wanted to report that Sage-4.6-r1 shows exactly the same
> > 
> > behaviour with python-2.6.6-r1.
> > 
> > -----
> > 
> >  <v_2e@ukr.net>



  reply	other threads:[~2010-11-29 10:43 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
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 [this message]
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=201011291143.10495.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