Concerning the failure of a test by guava.py, a new version of guava should be
coming out soon. I'll try running test on that instead.


On 8/7/07, JMD <[EMAIL PROTECTED]> wrote:
>
>
>
> Finally sage compilation fails on slamd64, even without supplementary
> optimization, with the error quoted above. Here we have gcc 3.4.6
>
> ---------------------------------------------------------------------------------------------------------
> ---------------------------------------------------------------------------------------------------------
>
> I tried to do it on gentoo for x86_64 :
> Linux 2.6.19 #4 SMP Tue Dec 19 09:08:26 CET 2006 x86_64 AMD Athlon(tm)
> 64 X2 Dual Core Processor 4200+ AuthenticAMD GNU/Linux
>
> Here we have gcc 4.1.2.   I have tried with and without optimization.
> The compilation succeeds in the two cases
>
> ------------------------------------------------------------
> with no optimization there is only one error in the tests :
>
> sage -t  coding/guava.py
> **********************************************************************
> File "guava.py", line 280:
>     sage: C = CyclicCode(g,7,GF(2))
> Exception raised:
>     Traceback (most recent call last):
>       File "/xd1/sage-2.7.3/local/lib/python2.5/doctest.py", line
> 1212, in __run
>         compileflags, 1) in test.globs
>       File "<doctest __main__.example_7[2]>", line 1, in <module>
>         C = CyclicCode(g,Integer(7),GF(Integer(2)))###line 280:
>     sage: C = CyclicCode(g,7,GF(2))
>       File "/xd1/sage-2.7.3/local/lib/python2.5/site-packages/sage/
> coding/guava.py", line 290, in CyclicCode
>         gap.eval("C:=GeneratorPolCode("+gap_g+","+str(n)+", GF("+str(q)
> +"))")
>       File "/xd1/sage-2.7.3/local/lib/python2.5/site-packages/sage/
> interfaces/gap.py", line 300, in eval
>         s = Expect.eval(self, x)
>       File "/xd1/sage-2.7.3/local/lib/python2.5/site-packages/sage/
> interfaces/expect.py", line 523, in eval
>         return '\n'.join([self._eval_line(L, **kwds) for L in
> code.split('\n') if L != ''])
>       File "/xd1/sage-2.7.3/local/lib/python2.5/site-packages/sage/
> interfaces/gap.py", line 484, in _eval_line
>         raise RuntimeError, message
>     RuntimeError: Gap produced error output
>     Error, no 1st choice method found for `GeneratorPolCode' on 3
> arguments
>
>        executing C:=GeneratorPolCode(Z(2)^0,7, GF(2));
> **********************************************************************
> File "guava.py", line 281:
>     sage: C
> Exception raised:
>     Traceback (most recent call last):
>       File "/xd1/sage-2.7.3/local/lib/python2.5/doctest.py", line
> 1212, in __run
>         compileflags, 1) in test.globs
>       File "<doctest __main__.example_7[3]>", line 1, in <module>
>         C###line 281:
>     sage: C
>     NameError: name 'C' is not defined
> **********************************************************************
> 1 items had failures:
>    2 of   4 in __main__.example_7
> ***Test Failed*** 2 failures.
> For whitespace errors, see the file .doctest_guava.py
>
> ---------------------------------------------------------------------
>
>
>
>
>
>
>
>
>
> with the optimizations (CFLAGS ans CXXFLAGS="-O3 -mtune=k8") there are
> plenty of errors of type
>
> sage -t  interfaces/singular.py
>
> ------------------------------------------------------------
> 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).
> ------------------------------------------------------------
>
>
> A mysterious error (perphaps a memory error?) occured, which may have
> crashed doctest.
>
>
> and finally the program hangs at this point :
>
> sage -t  rings/fraction_field_element.py                    *** glibc
> detected *
> ** /xd1/sage-2.7.3/local/bin/python: double free or corruption
> (!prev): 0x00000000018c0270 ***
>
> A mysterious error (perphaps a memory error?) occured, which may have
> crashed doctest.
>
>
>
>
>
>
> --------------------------------------------------------------------------------------------
> --------------------------------------------------------------------------------------------
>
> Finally I have tried on a Inspiron 9300, with slackware 12.0.
>
> Linux 2.6.21.5-smp #2 SMP Tue Jun 19 14:58:11 CDT 2007 i686 Intel(R)
> Pentium(R) M processor 1.73GHz GenuineIntel GNU/Linux
>
>
> Here we have gcc 4.1.2
>
> Compilation succeeds and there is only one error in the tests :
>
> sage -t  rings/power_series_ring_element.pyx                *** ***
> Error: TIMED OUT! *** ***
> *** *** Error: TIMED OUT! *** ***
>          [188.3 s]
>
>
>
>
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
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