sage-4.3.rc2
William Stein
I've released sage-4.3.rc2. It's here:
http://sage.math.washington.edu/home/wstein/farm/src/sage-4.3.rc2.tar
This will be 4.3 if it checks out. Please test.
William
--
William Stein
Associate Professor of Mathematics
University of Washington
http://wstein.org
Jaap Spies
> Hi,
>
> I've released sage-4.3.rc2. It's here:
> http://sage.math.washington.edu/home/wstein/farm/src/sage-4.3.rc2.tar
>
> This will be 4.3 if it checks out. Please test.
>
On my new machine with quad core Intel i7 860 processor and Fedora 12-x86_64:
The following tests failed:
sage -t devel/sage/sage/numerical/mip.pyx # 1 doctests failed
sage -t devel/sage/sage/groups/generic.py # Segfault
sage -t devel/sage/sage/matrix/matrix_space.py # Segfault
sage -t devel/sage/sage/matrix/matrix_sparse.pyx # Segfault
sage -t devel/sage/sage/matrix/matrix2.pyx # Segfault
sage -t devel/sage/sage/schemes/elliptic_curves/ell_point.py # Segfault
sage -t devel/sage/sage/schemes/elliptic_curves/ell_finite_field.py # Segfault
sage -t devel/sage/sage/schemes/hyperelliptic_curves/hyperelliptic_generic.py
# Segfault
sage -t devel/sage/sage/schemes/hyperelliptic_curves/hyperelliptic_finite_field.py
# Segfault
sage -t devel/sage/sage/modules/free_module.py # Segfault
sage -t devel/sage/sage/tests/benchmark.py # Segfault
sage -t devel/sage/sage/schemes/elliptic_curves/ell_rational_field.py
# Segfault
sage -t devel/sage/sage/modular/ssmod/ssmod.py # Segfault
sage -t devel/sage/sage/modular/modform/ambient.py # Segfault
sage -t devel/sage/sage/modular/modsym/modsym.py # Segfault
sage -t devel/sage/sage/modular/modsym/space.py # Segfault
sage -t devel/sage/sage/rings/finite_field_morphism.py # Segfault
sage -t devel/sage/sage/rings/finite_field_ext_pari.py # Segfault
sage -t devel/sage/sage/rings/finite_field_ntl_gf2e.pyx # Segfault
sage -t devel/sage/sage/rings/polynomial/polynomial_quotient_ring_element.py
# Segfault
sage -t devel/sage/sage/rings/number_field/number_field_rel.py # Segfault
sage -t devel/sage/sage/rings/number_field/number_field.py # Segfault
sage -t devel/sage/sage/coding/code_constructions.py # Segfault
sage -t devel/sage/sage/coding/linear_code.py # Segfault
----------------------------------------------------------------------
Total time for all tests: 680.9 seconds
[jaap@vrede sage-4.3.rc2]$
No surprise, but intriguing what is causing this.
Jaap
William Stein
> Hi,
>
> I've released sage-4.3.rc2. It's here:
> http://sage.math.washington.edu/home/wstein/farm/src/sage-4.3.rc2.tar
>
> This will be 4.3 if it checks out. Please test.
>
One doctest fails and it fails to build on some OS X 10.x machines for
x <= 5, so I fixed both issues and made a new optimistic release:
http://sage.math.washington.edu/home/wstein/farm/src/sage-4.3.tar
William
William Stein
> On Thu, Dec 24, 2009 at 9:13 AM, William Stein <wst...@gmail.com> wrote:
>> Hi,
>>
>> I've released sage-4.3.rc2. It's here:
>> http://sage.math.washington.edu/home/wstein/farm/src/sage-4.3.rc2.tar
>>
>> This will be 4.3 if it checks out. Please test.
>>
>
> On my new machine with quad core Intel i7 860 processor and Fedora 12-x86_64:
>
This is definitely not a problem because of Fedora 12 or x86_64, since
I built the same rc2 on FC12 x86_64.
> The following tests failed:
>
> sage -t devel/sage/sage/numerical/mip.pyx # 1 doctests failed
> sage -t devel/sage/sage/groups/generic.py # Segfault
What exactly is segfaulting!? Find out with
sage -t --verbose devel/sage/sage/groups/generic.py
> No surprise, but intriguing what is causing this.
>
> Jaap
I don't have access to any core i7 computers. Does *anybody* else on this list?
William
> --
>
> You received this message because you are subscribed to the Google Groups "sage-release" group.
> To post to this group, send email to sage-r...@googlegroups.com.
> To unsubscribe from this group, send email to sage-release...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/sage-release?hl=en.
Jaap Spies
> On Thu, Dec 24, 2009 at 9:36 AM, Jaap Spies <jaap...@gmail.com> wrote:
>> On Thu, Dec 24, 2009 at 9:13 AM, William Stein <wst...@gmail.com> wrote:
>>> Hi,
>>>
>>> I've released sage-4.3.rc2. It's here:
>>> http://sage.math.washington.edu/home/wstein/farm/src/sage-4.3.rc2.tar
>>>
>>> This will be 4.3 if it checks out. Please test.
>>>
>>
>> On my new machine with quad core Intel i7 860 processor and Fedora 12-x86_64:
>>
>
> This is definitely not a problem because of Fedora 12 or x86_64, since
> I built the same rc2 on FC12 x86_64.
>
>> The following tests failed:
>>
>> sage -t devel/sage/sage/numerical/mip.pyx # 1 doctests failed
>> sage -t devel/sage/sage/groups/generic.py # Segfault
>
> What exactly is segfaulting!? Find out with
>
> sage -t --verbose devel/sage/sage/groups/generic.py
>
237 tests in 20 items.
237 passed and 0 failed.
Test passed.
[10.4 s]
exit code: 768
----------------------------------------------------------------------
The following tests failed:
sage -t --verbose "devel/sage/sage/groups/generic.py"
Total time for all tests: 10.4 seconds
I have seen this before :(
Jaap
William Stein
What about
sage -t --gdb devel/sage/sage/groups/generic.py
Jaap Spies
sage -t -gdb "devel/sage/sage/groups/generic.py"
********************************************************************************
Type r at the (gdb) prompt to run the doctests.
Type bt if there is a crash to see a traceback.
********************************************************************************
'import site' failed; use -v for traceback
Traceback (most recent call last):
File "<string>", line 27, in <module>
ImportError: No module named os.path
GNU gdb (GDB) Fedora (7.0-13.fc12)
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /home/jaap/downloads/sage-4.3.rc2/local/bin/python...done.
(gdb) r
Starting program: /home/jaap/downloads/sage-4.3.rc2/local/bin/python
/home/jaap/.sage//tmp/.doctest_generic.py
[Thread debugging using libthread_db enabled]
Traceback (most recent call last):
File "/usr/share/gdb/auto-load/usr/lib64/libstdc++.so.6.0.13-gdb.py",
line 19, in <module>
import os
ImportError: No module named os
Detaching after fork from child process 12539.
Program received signal SIGSEGV, Segmentation fault.
0x0000003d2d674695 in malloc_consolidate () from /lib64/libc.so.6
Missing separate debuginfos, use: debuginfo-install
expat-2.0.1-8.fc12.x86_64 fontconfig-2.8.0-1.fc12.x86_64
glibc-2.11-2.x86_64 keyutils-libs-1.2-6.fc12.x86_64
krb5-libs-1.7-10.fc12.x86_64 libX11-1.3-1.fc12.x86_64
libXau-1.0.5-1.fc12.x86_64 libXpm-3.5.8-2.fc12.x86_64
libcom_err-1.41.9-5.fc12.x86_64 libgcc-4.4.2-7.fc12.x86_64
libselinux-2.0.87-1.fc12.x86_64 libstdc++-4.4.2-7.fc12.x86_64
libxcb-1.4-2.fc12.x86_64 ncurses-libs-5.7-3.20090207.fc12.x86_64
nss-softokn-freebl-3.12.4-10.fc12.x86_64
openssl-1.0.0-0.13.beta4.fc12.x86_64
(gdb) bt
#0 0x0000003d2d674695 in malloc_consolidate () from /lib64/libc.so.6
#1 0x0000003d2d676fc8 in _int_free () from /lib64/libc.so.6
#2 0x0000003d2d635b72 in exit () from /lib64/libc.so.6
#3 0x00000000004bad2a in Py_Exit (sts=0) at Python/pythonrun.c:1716
#4 handle_system_exit (sts=0) at Python/pythonrun.c:1116
#5 0x00000000004baf45 in PyErr_PrintEx (set_sys_last_vars=1) at
Python/pythonrun.c:1126
#6 0x00000000004bbc90 in PyRun_SimpleFileExFlags (fp=<value optimized
out>, filename=<value optimized out>, closeit=1, flags=0x7fffffffd8e0)
at Python/pythonrun.c:935
#7 0x0000000000413caf in Py_Main (argc=<value optimized out>,
argv=<value optimized out>) at Modules/main.c:599
#8 0x0000003d2d61eb1d in __libc_start_main () from /lib64/libc.so.6
#9 0x0000000000412f09 in _start ()
(gdb)
Jaap
William Stein
Hmm. SELINUX? Can you try completely removing/disabling SELINUX?
Maybe that is causing trouble. It usually does.
William
> libstdc++-4.4.2-7.fc12.x86_64
> libxcb-1.4-2.fc12.x86_64 ncurses-libs-5.7-3.20090207.fc12.x86_64
> nss-softokn-freebl-3.12.4-10.fc12.x86_64
> openssl-1.0.0-0.13.beta4.fc12.x86_64
> (gdb) bt
> #0 0x0000003d2d674695 in malloc_consolidate () from /lib64/libc.so.6
> #1 0x0000003d2d676fc8 in _int_free () from /lib64/libc.so.6
> #2 0x0000003d2d635b72 in exit () from /lib64/libc.so.6
> #3 0x00000000004bad2a in Py_Exit (sts=0) at Python/pythonrun.c:1716
> #4 handle_system_exit (sts=0) at Python/pythonrun.c:1116
> #5 0x00000000004baf45 in PyErr_PrintEx (set_sys_last_vars=1) at
> Python/pythonrun.c:1126
> #6 0x00000000004bbc90 in PyRun_SimpleFileExFlags (fp=<value optimized
> out>, filename=<value optimized out>, closeit=1, flags=0x7fffffffd8e0)
> at Python/pythonrun.c:935
> #7 0x0000000000413caf in Py_Main (argc=<value optimized out>,
> argv=<value optimized out>) at Modules/main.c:599
> #8 0x0000003d2d61eb1d in __libc_start_main () from /lib64/libc.so.6
> #9 0x0000000000412f09 in _start ()
> (gdb)
>
> Jaap
>
Nathann Cohen
> the failure.
Sorryyyyyyyyyyy !!! I learnt from one of William's posts this came
from different hash on different platforms.... I will remember to sort
them before printing them next time :-)
Nathann
Jaap Spies
> On Thu, Dec 24, 2009 at 10:24 AM, Jaap Spies <jaap...@gmail.com> wrote:
>> On Thu, Dec 24, 2009 at 7:18 PM, William Stein <wst...@gmail.com> wrote:
> Hmm. SELINUX? Can you try completely removing/disabling SELINUX?
> Maybe that is causing trouble. It usually does.
>
No, I'm used to disable SELINUX just after install!!!!
I agree it is a pain in the ... for a user like me.
Jaap
> William
William Stein
Please referee
http://trac.sagemath.org/sage_trac/ticket/7758
which sorts the variables by string representation.
William
William Stein
Evidently, you didn't fully disable it since the selinux library is
listed right in your previous email:
> libselinux-2.0.87-1.fc12.x86_64
William
Jaap Spies
Don't know how to disable it more?
What did you do on your install of Fedora 12?\
Jaap
William Stein
>>> No, I'm used to disable SELINUX just after install!!!!
>>> I agree it is a pain in the ... for a user like me.
>>
>> Evidently, you didn't fully disable it since the selinux library is
>> listed right in your previous email:
>>
>>> libselinux-2.0.87-1.fc12.x86_64
>>
>
> Don't know how to disable it more?
>
> What did you do on your install of Fedora 12?
I'm not the sysadmin of that box.
Here's the output for me, when I test with gdb. There is a mention of
the selinux library, so I was wrong that this is relevant to your
problem. So now we're still stumped... at least until I get access to
a core i7.
[wstein@eno sage-4.3.rc2]$ ./sage -t --gdb devel/sage/sage/groups/generic.py
sage -t --gdb "devel/sage/sage/groups/generic.py"
********************************************************************************
Type r at the (gdb) prompt to run the doctests.
Type bt if there is a crash to see a traceback.
********************************************************************************
'import site' failed; use -v for traceback
Traceback (most recent call last):
File "<string>", line 27, in <module>
ImportError: No module named os.path
GNU gdb (GDB) Fedora (7.0-9.fc12)
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from
/home/wstein/screen/eno/sage-4.3.rc2/local/bin/python...done.
(gdb) r
Starting program:
/home/wstein/screen/eno/sage-4.3.rc2/local/bin/python
/home/wstein/.sage//tmp/.doctest_generic.py
[Thread debugging using libthread_db enabled]
Detaching after fork from child process 31776.
Program exited normally.
Missing separate debuginfos, use: debuginfo-install
expat-2.0.1-8.fc12.x86_64 fontconfig-2.8.0-1.fc12.x86_64
glibc-2.11-2.x86_64 keyutils-libs-1.2-6.fc12.x86_64
krb5-libs-1.7-10.fc12.x86_64 libX11-1.3-1.fc12.x86_64
libXau-1.0.5-1.fc12.x86_64 libXpm-3.5.8-2.fc12.x86_64
libcom_err-1.41.9-5.fc12.x86_64 libselinux-2.0.87-1.fc12.x86_64
libxcb-1.4-2.fc12.x86_64 ncurses-libs-5.7-3.20090207.fc12.x86_64
nss-softokn-freebl-3.12.4-10.fc12.x86_64
openssl-1.0.0-0.13.beta4.fc12.x86_64
(gdb)
(gdb) quit
[28.2 s]
----------------------------------------------------------------------
All tests passed!
Total time for all tests: 28.2 seconds
[wstein@eno sage-4.3.rc2]$
[wstein@eno sage-4.3.rc2]$ cat /etc/issue
Fedora release 12 (Constantine)
Kernel \r on an \m (\l)
[wstein@eno sage-4.3.rc2]$ uname -a
Linux eno 2.6.31.6-166.fc12.x86_64 #1 SMP Wed Dec 9 10:46:22 EST 2009
x86_64 x86_64 x86_64 GNU/Linux
[wstein@eno sage-4.3.rc2]$
Jaap Spies
>>
>>>> No, I'm used to disable SELINUX just after install!!!!
>>>> I agree it is a pain in the ... for a user like me.
>>>
>>> Evidently, you didn't fully disable it since the selinux library is
>>> listed right in your previous email:
>>>
>>>> libselinux-2.0.87-1.fc12.x86_64
>>>
>>
>> Don't know how to disable it more?
>>
>> What did you do on your install of Fedora 12?
>
> I'm not the sysadmin of that box.
>
> Here's the output for me, when I test with gdb. There is a mention of
> the selinux library, so I was wrong that this is relevant to your
> problem. So now we're still stumped... at least until I get access to
> a core i7.
>
Yeah, let me know what I can do.
Most failures give a backtrace like:
*** glibc detected *** python: double free or corruption (fasttop):
0x000000000310b1b0 ***
======= Backtrace: =========
/lib64/libc.so.6[0x3d2d674576]
/lib64/libc.so.6(exit+0xe2)[0x3d2d635b72]
python[0x4bad2a]
python(PyErr_PrintEx+0x1a5)[0x4baf45]
python(PyRun_SimpleFileExFlags+0x1e0)[0x4bbc90]
python(Py_Main+0x9af)[0x413caf]
/lib64/libc.so.6(__libc_start_main+0xfd)[0x3d2d61eb1d]
python[0x412f09]
======= Memory map: ========
00400000-00552000 r-xp 00000000 fd:00 1461872
/home/jaap/downloads/sage-4.3.rc1/local/bin/python
00751000-0078a000 rw-p 00151000 fd:00 1461872
/home/jaap/downloads/sage-4.3.rc1/local/bin/python
0078a000-00798000 rw-p 00000000 00:00 0
010bb000-057c2000 rw-p 00000000 00:00 0 [heap]
33eca00000-33eca34000 r-xp 00000000 fd:00 266329
/usr/lib64/libfontconfig.so.1.4.4
33eca34000-33ecc34000 ---p 00034000 fd:00 266329
/usr/lib64/libfontconfig.so.1.4.4
33ecc34000-33ecc36000 rw-p 00034000 fd:00 266329
/usr/lib64/libfontconfig.so.1.4.4
3494600000-349461b000 r-xp 00000000 fd:00 324757
/usr/lib64/libxcb.so.1.1.0
349461b000-349481a000 ---p 0001b000 fd:00 324757
/usr/lib64/libxcb.so.1.1.0
349481a000-349481b000 rw-p 0001a000 fd:00 324757
/usr/lib64/libxcb.so.1.1.0
3494a00000-3494b39000 r-xp 00000000 fd:00 324758
/usr/lib64/libX11.so.6.3.0
3494b39000-3494d39000 ---p 00139000 fd:00 324758
/usr/lib64/libX11.so.6.3.0
3494d39000-3494d3f000 rw-p 00139000 fd:00 324758
/usr/lib64/libX11.so.6.3.0
3495600000-3495626000 r-xp 00000000 fd:00 131584
/lib64/libexpat.so.1.5.2
3495626000-3495825000 ---p 00026000 fd:00 131584
/lib64/libexpat.so.1.5.2
3495825000-3495828000 rw-p 00025000 fd:00 131584
/lib64/libexpat.so.1.5.2
3497200000-34972b3000 r-xp 00000000 fd:00 131849
/lib64/libkrb5.so.3.3
34972b3000-34974b3000 ---p 000b3000 fd:00 131849
/lib64/libkrb5.so.3.3
34974b3000-34974bd000 rw-p 000b3000 fd:00 131849
/lib64/libkrb5.so.3.3
3497600000-3497608000 r-xp 00000000 fd:00 131836
/lib64/libkrb5support.so.0.1
3497608000-3497808000 ---p 00008000 fd:00 131836
/lib64/libkrb5support.so.0.1
3497808000-3497809000 rw-p 00008000 fd:00 131836
/lib64/libkrb5support.so.0.1
3497a00000-3497a2a000 r-xp 00000000 fd:00 131848
/lib64/libk5crypto.so.3.1
3497a2a000-3497c2a000 ---p 0002a000 fd:00 131848
/lib64/libk5crypto.so.3.1
3497c2a000-3497c2c000 rw-p 0002a000 fd:00 131848
/lib64/libk5crypto.so.3.1
3498200000-349822d000 r-xp 00000000 fd:00 131851
/lib64/libgssapi_krb5.so.2.2
349822d000-349842d000 ---p 0002d000 fd:00 131851
/lib64/libgssapi_krb5.so.2.2
349842d000-349842f000 rw-p 0002d000 fd:00 131851
/lib64/libgssapi_krb5.so.2.2
3498600000-3498652000 r-xp 00000000 fd:00 269879
/usr/lib64/libssl.so.1.0.0
3498652000-3498851000 ---p 00052000 fd:00 269879
/usr/lib64/libssl.so.1.0.0
3498851000-3498859000 rw-p 00051000 fd:00 269879
/usr/lib64/libssl.so.1.0.0
349aa00000-349aa11000 r-xp 00000000 fd:00 332339
/usr/lib64/libXpm.so.4.11.0
349aa11000-349ac10000 ---p 00011000 fd:00 332339
/usr/lib64/libXpm.so.4.11.0
349ac10000-349ac11000 rw-p 00010000 fd:00 332339
/usr/lib64/libXpm.so.4.11.0
3d2d200000-3d2d21e000 r-xp 00000000 fd:00 131831
/lib64/ld-2.11.so
3d2d41d000-3d2d41e000 r--p 0001d000 fd:00 131831
/lib64/ld-2.11.so
3d2d41e000-3d2d41f000 rw-p 0001e000 fd:00 131831
/lib64/ld-2.11.so
3d2d41f000-3d2d420000 rw-p 00000000 00:00 0
3d2d600000-3d2d76f000 r-xp 00000000 fd:00 131832
/lib64/libc-2.11.so
3d2d76f000-3d2d96e000 ---p 0016f000 fd:00 131832
/lib64/libc-2.11.so
3d2d96e000-3d2d972000 r--p 0016e000 fd:00 131832
/lib64/libc-2.11.so
3d2d972000-3d2d973000 rw-p 00172000 fd:00 131832
/lib64/libc-2.11.so
3d2d973000-3d2d978000 rw-p 00000000 00:00 0
3d2da00000-3d2da83000 r-xp 00000000 fd:00 131833
/lib64/libm-2.11.so
3d2da83000-3d2dc82000 ---p 00083000 fd:00 131833
/lib64/libm-2.11.so
3d2dc82000-3d2dc83000 r--p 00082000 fd:00 131833
/lib64/libm-2.11.so
3d2dc83000-3d2dc84000 rw-p 00083000 fd:00 131833
/lib64/libm-2.11.so
3d2de00000-3d2de02000 r-xp 00000000 fd:00 131835
/lib64/libdl-2.11.so
3d2de02000-3d2e002000 ---p 00002000 fd:00 131835
/lib64/libdl-2.11.so
3d2e002000-3d2e003000 r--p 00002000 fd:00 131835
/lib64/libdl-2.11.so
3d2e003000-3d2e004000 rw-p 00003000 fd:00 131835
/lib64/libdl-2.11.so
3d2e200000-3d2e217000 r-xp 00000000 fd:00 131838
/lib64/libpthread-2.11.so
3d2e217000-3d2e416000 ---p 00017000 fd:00 131838
/lib64/libpthread-2.11.so
3d2e416000-3d2e417000 r--p 00016000 fd:00 131838
/lib64/libpthread-2.11.so
3d2e417000-3d2e418000 rw-p 00017000 fd:00 131838
/lib64/libpthread-2.11.so
3d2e418000-3d2e41c000 rw-p 00000000 00:00 0
3d2ea00000-3d2ea07000 r-xp 00000000 fd:00 131855
/lib64/librt-2.11.so
3d2ea07000-3d2ec06000 ---p 00007000 fd:00 131855
/lib64/librt-2.11.so
3d2ec06000-3d2ec07000 r--p 00006000 fd:00 131855
/lib64/librt-2.11.so
3d2ec07000-3d2ec08000 rw-p 00007000 fd:00 131855
/lib64/librt-2.11.so
3d2ee00000-3d2ee1c000 r-xp 00000000 fd:00 131847
/lib64/libselinux.so.1sage -t devel/sage/sage/coding/linear_code.py
A mysterious error (perhaps a memory error?) occurred, which may have
crashed doctest.
[26.3 s]
Jaap
William Stein
I can't help but wonder what happens if you delete (move out of the
way) libselinux.so.1...
Otherwise, given the error, you should install the latest valgrind,
rebuild Sage to use it, etc. This would be a perfect job for
mabshoff++.
William
sage -t devel/sage/sage/coding/linear_code.py
> A mysterious error (perhaps a memory error?) occurred, which may have
> crashed doctest.
> [26.3 s]
>
> Jaap
>
Jaap Spies
> On Thu, Dec 24, 2009 at 12:55 PM, Jaap Spies <jaap...@gmail.com> wrote:
>> On Thu, Dec 24, 2009 at 9:46 PM, William Stein <wst...@gmail.com> wrote:
>>>>
>>>>>> No, I'm used to disable SELINUX just after install!!!!
>>>>>> I agree it is a pain in the ... for a user like me.
>>>>>
>>>>> Evidently, you didn't fully disable it since the selinux library is
>>>>> listed right in your previous email:
>>>>>
>>>>>> libselinux-2.0.87-1.fc12.x86_64
>>>>>
>>>>
>>>> Don't know how to disable it more?
>>>>
>>>> What did you do on your install of Fedora 12?
>>>
>>> I'm not the sysadmin of that box.
>>>
>>> Here's the output for me, when I test with gdb. There is a mention of
>>> the selinux library, so I was wrong that this is relevant to your
>>> problem. So now we're still stumped... at least until I get access to
>>> a core i7.
>>>
>>
>> Yeah, let me know what I can do.
>>
>
> I can't help but wonder what happens if you delete (move out of the
> way) libselinux.so.1...
>
I'll try.
> Otherwise, given the error, you should install the latest valgrind,
> rebuild Sage to use it, etc. This would be a perfect job for
> mabshoff++.
>
+10!
Michael does not answer my e-mails I send him lately. I'm concerned.
Jaap
> William
>
William Stein
By "mabshoff++", I meant whoever the successor to Michael will be
regarding using Valgrind effectively.
William
Jaap Spies
> On Thu, Dec 24, 2009 at 1:04 PM, Jaap Spies <jaap...@gmail.com> wrote:
> By "mabshoff++", I meant whoever the successor to Michael will be
> regarding using Valgrind effectively.
>
Let's hope somebody will show up.
Jaap
> William
Robert Miller
>> regarding using Valgrind effectively.
>>
> ++
>
> Let's hope somebody will show up.
There is a very clear set of instructions here:
http://wiki.sagemath.org/ValgrindingSage
Anyone can do it! And I've done it several times already.
--
Robert L. Miller
http://www.rlmiller.org/
William Stein
>>> By "mabshoff++", I meant whoever the successor to Michael will be
>>> regarding using Valgrind effectively.
>>>
>> ++
>>
>> Let's hope somebody will show up.
>
> There is a very clear set of instructions here:
>
> http://wiki.sagemath.org/ValgrindingSage
>
> Anyone can do it! And I've done it several times already.
>
I know you could. But please, please work on your Ph.D. thesis instead.
William
Jaap Spies
>>> By "mabshoff++", I meant whoever the successor to Michael will be
>>> regarding using Valgrind effectively.
>>>
>> ++
>>
>> Let's hope somebody will show up.
>
Hi,
> There is a very clear set of instructions here:
>
> http://wiki.sagemath.org/ValgrindingSage
>
> Anyone can do it! And I've done it several times already.
>
I tried, but the optional package did not build in Fedora 12-x86_64:
glibc-2.11 is not supported.
Even the last stable release valgrind-3.5.0 did not work.
I made a new spkg from svn: valgrind-3.6.0.svn.spkg that eventually
could be installed.
See: http://sage.math.washington.edu/home/jsp/valgrind-3.6.0.svn.spkg
Needs a maintainer: *not me*!
Seems to work for me on Fedora 12 with sage-4.3
Will open a ticket some time in the future.
Jaap
> --
> Robert L. Miller
> http://www.rlmiller.org/
>