On 15 Okt., 09:48, Jan Groenewald <j...@aims.ac.za> wrote:
> Summary: On a mixture of sage 4.5.2, 4.5.3, and 4.6alpha3
>
> Linux:
> i7 64bit: sefgault
> E8400 64bit: segfault
> T4300 64bit: segfault
> T3200 64bit: segfault
> T2300 32bit: no segfault
>
> OS X 10.6 (Marshall: 32 or 64 bit?): no segfault
>
> Conjecture: It is a Linux specific 64bit problem.
>
> Can some people on 32bit and 64bit and different CPUs (amd as well)
> send in the output of
>
> grep name /proc/cpuifo
> uname -a
> sage -v
> sage -t devel/sage/sage/interfaces/sage0.py
> dmesg|grep pari
Summary:
I didn't get any segfaults with Sage 4.6.{alpha*,rc0}, upgraded or
built from scratch on
* Ubuntu 9.04 x86 (32-bit Pentium 4 Prescott, gcc 4.3.3)
* Ubuntu 9.04 x86_64 (Core2, gcc 4.3.3)
* Ubuntu 10.04 x86_64 (Core2, gcc 4.4.3)
(I've built or upgraded to these dozens of times on those
machines... ;-) )
Those people getting the segfaults should perhaps delete $SAGE_ROOT/
local/lib/libpari-gmp.* if they exist, rerun the doctests and see if
they really get /new/ messages from dmesg. (I personally rarely reboot
my machines; "sudo dmesg -c" clears previous logs.)
-Leif
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
