One more data point: on Ubuntu 10.10, sage-4.6.alpha3,
grep /proc/cpuinfo
model name : Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
uname -a:
Linux sancho 2.6.35-22-generic #34-Ubuntu SMP Sun Oct 10 09:26:05 UTC
2010 x86_64 GNU/Linu
I do not get the segfault.
-Marshall
On Oct 15, 3:31 am
Hi Karl-Dieter and Burcin,
You wrote (I cut a lot)
Yup, I see what you are talking about - e.g.
if (x.is_equal(_ex1)) // log(1) -> 0
return _ex0;
Although it might be nice to stay relatively close to Ginac and fix
such things on the Sage level if that's
On Oct 15, 2:02 pm, Burcin Erocal wrote:
> Hi Karl-Dieter,
>
> On Fri, 15 Oct 2010 10:09:50 -0700 (PDT)
>
>
>
>
>
> kcrisman wrote:
> > --
> > | Sage Version 4.6.alpha3, Release Date: 2010-10-08 |
> > | Type no
Ok I found a workarround:
I enlarged the ranges in the for loop for the search of the functions.
The change apparently made the search range for the function foo
wider.
All doctests pass now
Open question why does this work if I type it in by hand...
On 14 Okt., 21:57, maldun wrote:
> Hi all!
>
Hi Karl-Dieter,
On Fri, 15 Oct 2010 10:09:50 -0700 (PDT)
kcrisman wrote:
> --
> | Sage Version 4.6.alpha3, Release Date: 2010-10-08 |
> | Type notebook() for the GUI, and license() for information.|
> --
Dear all, but mostly Burcin,
--
| Sage Version 4.6.alpha3, Release Date: 2010-10-08 |
| Type notebook() for the GUI, and license() for information.|
On 10/15/10 3:15 AM, Jan Groenewald wrote:
Hi
On Fri, Oct 15, 2010 at 03:02:07AM -0500, Jason Grout wrote:
Hope that helps.
So it is NOT 64bit specific. Perhaps it is Ubuntu specific.
Uhm no, Jason had ubuntu there.
10.04.1, I believe.
Thanks,
Jason
--
To post to this group, send an
I think it is better to move this discussion to the trac page
http://trac.sagemath.org/sage_trac/ticket/7893
--
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 thi
Also, I can NOT reproduce the segfault on the following system with
sage-4.6.alpha3:
$ Linux arcanis 2.6.32-gentoo-r7 #5 SMP Thu Jun 10 23:07:26 CEST 2010
x86_64 Intel(R) Core(TM)2 Duo CPU T5870 @ 2.00GHz GenuineIntel GNU/Linux
$ gcc --version
gcc-4.4.3 (Gentoo 4.4.3-r2 p1.2) 4.4.3
Copyright (C) 2
Hi
> On Fri, Oct 15, 2010 at 03:02:07AM -0500, Jason Grout wrote:
> > Hope that helps.
>
> So it is NOT 64bit specific. Perhaps it is Ubuntu specific.
Uhm no, Jason had ubuntu there.
Jan
--
.~.
/V\ Jan Groenewald
/( )\www.aims.ac.za
^^-^^
--
To post to this group, send an
Hi
On Fri, Oct 15, 2010 at 03:02:07AM -0500, Jason Grout wrote:
> Hope that helps.
So it is NOT 64bit specific. Perhaps it is Ubuntu specific.
Jan
--
.~.
/V\ Jan Groenewald
/( )\www.aims.ac.za
^^-^^
--
To post to this group, send an email to sage-devel@googlegroups.com
To
On 10/15/10 2:48 AM, Jan Groenewald wrote:
Hi
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 Lin
Hi
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 o
Hi Kwankyu,
Thanks for your work. Here are some comments for the current version:
49 os.kill(pid,signal.SIGTERM)
50 time.sleep(.5)
51 if os.path.isfile(pid_file):
52 print "Waiting for the sage server to terminate..."
53 ti
14 matches
Mail list logo
