On Nov 28, 9:00 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> On Nov 28, 2007 11:44 AM, mabshoff

<SNIP>

> > Odd. What happens if you do "export SAGE_CHECK=yes" and then rebuild
> > mpfr.spkg? Does the test suite pass?
>
> RQDF has nothing to do with mpfr.  It's the quaddouble*.spkg which is 100%
> independent of GMP/MPFR.

Oh well, maybe I should pay attention once in a while.

>  That said, if you build quaddouble directly and
> run its test suite, what happens.

I think I nailed down a potential cause:

==26107== Conditional jump or move depends on uninitialised value(s)
==26107==    at 0xC4BCC67:
__pyx_f_4sage_5rings_9real_rqdf_17QuadDoubleElement__set(__pyx_obj_4sage_5rings_9real_rqdf_QuadDo
ubleElement*, _object*) (real_rqdf.cpp:2521)
==26107==    by 0xC4B6037:
__pyx_pf_4sage_5rings_9real_rqdf_17QuadDoubleElement___init__(_object*,
_object*, _object*) (real
_rqdf.cpp:4282)
==26107==    by 0x459220: type_call (typeobject.c:436)
==26107==    by 0x415522: PyObject_Call (abstract.c:1860)
==26107==    by 0x47C850: PyEval_CallObjectWithKeywords (ceval.c:3433)
==26107==    by 0xC4B94F6:
__pyx_pf_4sage_5rings_9real_rqdf_25RealQuadDoubleField_class___call__(_object*,
_object*, _object
*) (real_rqdf.cpp:2919)
==26107==    by 0x415522: PyObject_Call (abstract.c:1860)
==26107==    by 0x481E91: PyEval_EvalFrameEx (ceval.c:3775)
==26107==    by 0x484F3A: PyEval_EvalCodeEx (ceval.c:2831)
==26107==    by 0x483CC4: PyEval_EvalFrameEx (ceval.c:494)
==26107==    by 0x484F3A: PyEval_EvalCodeEx (ceval.c:2831)
==26107==    by 0x48365C: PyEval_EvalFrameEx (ceval.c:3660)


==26107== Invalid read of size 1
==26107==    at 0x4A1CA13: strlen (mc_replace_strmem.c:242)
==26107==    by 0x44DA4A: PyString_FromString (stringobject.c:108)
==26107==    by 0xC4B81B8:
__pyx_pf_4sage_5rings_9real_rqdf_17QuadDoubleElement___str_no_scientific(_object*,
_object*) (rea
l_rqdf.cpp:5315)
==26107==    by 0x415522: PyObject_Call (abstract.c:1860)
==26107==    by 0x47C850: PyEval_CallObjectWithKeywords (ceval.c:3433)
==26107==    by 0xC4BB34A:
__pyx_pf_4sage_5rings_9real_rqdf_17QuadDoubleElement_str(_object*,
_object*) (real_rqdf.cpp:5851)
==26107==    by 0x415522: PyObject_Call (abstract.c:1860)
==26107==    by 0x47C850: PyEval_CallObjectWithKeywords (ceval.c:3433)
==26107==    by 0xC4B595B:
__pyx_pf_4sage_5rings_9real_rqdf_17QuadDoubleElement___repr__(_object*)
(real_rqdf.cpp:5153)
==26107==    by 0x442FF9: PyObject_Repr (object.c:361)
==26107==    by 0x429B3B: PyFile_WriteObject (fileobject.c:2196)
==26107==    by 0x4AC158: sys_displayhook (sysmodule.c:114)

==26107== Invalid read of size 1
==26107==    at 0x4A1DA5F: memcpy (mc_replace_strmem.c:402)
==26107==    by 0x44DAB2: PyString_FromString (stringobject.c:136)
==26107==    by 0xC4B81B8:
__pyx_pf_4sage_5rings_9real_rqdf_17QuadDoubleElement___str_no_scientific(_object*,
_object*) (rea
l_rqdf.cpp:5315)
==26107==    by 0x415522: PyObject_Call (abstract.c:1860)
==26107==    by 0x47C850: PyEval_CallObjectWithKeywords (ceval.c:3433)
==26107==    by 0xC4BB34A:
__pyx_pf_4sage_5rings_9real_rqdf_17QuadDoubleElement_str(_object*,
_object*) (real_rqdf.cpp:5851)
==26107==    by 0x415522: PyObject_Call (abstract.c:1860)
==26107==    by 0x47C850: PyEval_CallObjectWithKeywords (ceval.c:3433)
==26107==    by 0xC4B595B:
__pyx_pf_4sage_5rings_9real_rqdf_17QuadDoubleElement___repr__(_object*)
(real_rqdf.cpp:5153)
==26107==    by 0x442FF9: PyObject_Repr (object.c:361)
==26107==    by 0x429B3B: PyFile_WriteObject (fileobject.c:2196)
==26107==    by 0x4AC158: sys_displayhook (sysmodule.c:114)

Feel free to open a track ticket and send a patch :) - I am hunting a
dozen bugs on my own.

> Regarding the flint problem, that was caused by a problem with how the spkg
> was configured -- it should have turned off funroll_loops but it
> didn't correctly
> do so (it used to).
>

Cool.

>  -- William

Cheers,

Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-support@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-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~----------~----~----~----~------~----~------~--~---

Reply via email to