Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mpfr-3.0 breaks real_mpfr.pyx #13

Closed
kiwifb opened this issue Jun 24, 2010 · 6 comments
Closed

mpfr-3.0 breaks real_mpfr.pyx #13

kiwifb opened this issue Jun 24, 2010 · 6 comments

Comments

@kiwifb
Copy link
Collaborator

kiwifb commented Jun 24, 2010

After updating everything to mpfr-3.0 I got a nasty doctest failure:

francois@vrooom ~ $ sage -t  -force_lib "devel/sage/sage/rings/real_mpfr.pyx"
sage -t -force_lib "devel/sage/sage/rings/real_mpfr.pyx"    


------------------------------------------------------------
Unhandled SIGSEGV: A segmentation fault occured in Sage.
This probably occured because a *compiled* component
of Sage has a bug in it (typically accessing invalid memory)
or is not properly wrapped with _sig_on, _sig_off.
You might want to run Sage under gdb with 'sage -gdb' to debug this.
Sage will now terminate (sorry).
------------------------------------------------------------


         [5.5 s]
 
----------------------------------------------------------------------
The following tests failed:


        sage -t -force_lib "devel/sage/sage/rings/real_mpfr.pyx"
Total time for all tests: 5.5 seconds

The hunt revealed that the failure comes from this particular test:

sage: R = RealField(2147483647)


------------------------------------------------------------
Unhandled SIGSEGV: A segmentation fault occured in Sage.
This probably occured because a *compiled* component
of Sage has a bug in it (typically accessing invalid memory)
or is not properly wrapped with _sig_on, _sig_off.
You might want to run Sage under gdb with 'sage -gdb' to debug this.
Sage will now terminate (sorry).
------------------------------------------------------------

It could be caused by some memory constraint on my machine,
may be mpfr uses more memory. This particular value is 2^31-1 and
is meant to be the maximum precision that can be set for mpfr.
A few test show that on my machine the correct value is 2^31-2^5,
that is 2^31-2^5+1 leads to the segfault while the previous value is safe.

@cschwan
Copy link
Owner

cschwan commented Jun 24, 2010

Same here on x86 - looks like Sage needs some work on it

@cschwan
Copy link
Owner

cschwan commented Jun 26, 2010

Works fine on amd64.

@kiwifb
Copy link
Collaborator Author

kiwifb commented Jan 17, 2012

http://trac.sagemath.org/sage_trac/ticket/11666 not ready for inclusion as the 32bit issue is still not resolved.

@burcin
Copy link

burcin commented Mar 14, 2012

#11666 was merged in Sage-5.0.beta7. I guess this issue can be closed.

@kiwifb
Copy link
Collaborator Author

kiwifb commented Mar 14, 2012

I'll close it when 5.0 becomes "stable". In the main time I am keeping it open so people using 4.8 don't find it and open an issue for it. We could always backport it to sage-4.8 if 5.0 takes too long I guess.

@kiwifb
Copy link
Collaborator Author

kiwifb commented May 24, 2012

OK, as promised I am closing this. I'll probably purge sage 4.8 next week somewhere in my increasingly insane schedule.

@kiwifb kiwifb closed this as completed May 24, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants