On Aug 31, 12:47 am, "William Stein" <[EMAIL PROTECTED]> wrote:
> On 8/30/07, Martin Albrecht <[EMAIL PROTECTED]> wrote:
>
> > On Thursday 30 August 2007 19:11, mabshoff wrote:
> > > > On a suse 101. amd64: SAGE compiled file. The sage -testall
> > > > The above crash looks pretty serious -- it's evidently a 64-bit only
> > > > issue, which was probably introduced by our work to fix other bugs (??)
> > > > and/or memory leaks. This will be a blocker that has to be fixed before
> > > > sage-2.8.3 can be released.
>
> > I cannot reproduce this on my 64-bit Core2Duo system, i.e. 'make test'
> > passes.
> > So it is not a generic 64-bit problem.
>
> I'm dubious. On sage.math (an opteron) it breaks, and on my desktop intel
> Mac running 64-bit Linux (Xeon) it also fails.
>
> This is a pretty serious problem, whatever it is.
>
> William
There is hope: A potential source of the problem has been indentified.
To quote #sage-devel:
16:20 < was_> OK.
16:20 < was_> There are two versions of mpz_pylong in the SAGE source
code.
16:20 < was_> that's what is causing the trouble.
16:20 < was_> one is in ~/dist/s/dist/sage-2.8.3.rc3/devel/sage/sage/
ext$
16:21 < was_> The other is in ~/dist/s/dist/sage-2.8.3.rc3/devel/sage/
c_lib
16:21 < mabshoff> Aha
16:24 < craigcitro> it looks like joel might have just been working
from an old version or something; the two files only
differ in one place -- joel's version in c_lib
doesn't have mpz_get_pyintlong (david harvey just added
that a week or so ago, apparently)
16:24 < was_> scary.
A fix has been implemented and William is currently spinning an rc4.
Stay tuned.
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---
