You're right... I really should go to bed now =)
Well then it works also for ubuntu ^^
-maldun
On 10 Okt., 23:07, Mike Hansen wrote:
> On Sun, Oct 10, 2010 at 2:05 PM, maldun wrote:
> > Thanks to your patch the segfault is now gone, but apperently a new
> > problem arises:
>
> That is what is s
On Sun, Oct 10, 2010 at 2:05 PM, maldun wrote:
> Thanks to your patch the segfault is now gone, but apperently a new
> problem arises:
That is what is supposed to happen. There's no way to convert (x-a)
to a polynomial over the reals since "-a" cannot be converted to a
real number.
--Mike
--
On 10 Okt., 20:47, Mike Hansen wrote:
> On Sun, Oct 10, 2010 at 11:15 AM, maldun wrote:
> > sage: sage: a = var('a')
> > sage: sage: R. = a.parent()[]
> > sage: sage: (x - a).change_ring(RR) # boom!
>
> I've posted a patch athttp://trac.sagemath.org/sage_trac/ticket/10100
> which fixes this.
>
>
On 10/10/10 06:18 PM, maldun wrote:
8131979/home/maldun/sage/sage-4.5.3/devel/sage-
numpy-1.5/build/sage/finance/fractal.so
Program received signal SIGABRT, Aborted.
0x76e2ba75 in *__GI_raise (sig=) at ../
nptl/sysdeps/unix/sysv/linux/raise.c:64
64 ../nptl/sysdeps
On Sun, Oct 10, 2010 at 11:15 AM, maldun wrote:
> sage: sage: a = var('a')
> sage: sage: R. = a.parent()[]
> sage: sage: (x - a).change_ring(RR) # boom!
I've posted a patch at http://trac.sagemath.org/sage_trac/ticket/10100
which fixes this.
--Mike
--
To post to this group, send an email to s
Ok I know your problem. I use ubuntu 10.04 myself.
I built my own valgrind with source from svn to get it running.
Since we have the quite the same system I tried it out myself, and
voila...
valgrind gives no valuable information, except that it's a segfault:
sage: sage: a = var('a')
sage: sage
Ok I know your problem. I use ubuntu 10.04 myself.
I built my own valgrind with source from svn to get it running.
Since we have the quite the same system I tried it out myself, and
voila...
valgrind gives no valuable information, except that it's a segfault:
sage: sage: a = var('a')
sage: sage
Ok I know your problem. I use ubuntu 10.04 myself.
I built my own valgrind with source from svn to get it running.
Since we have the quite the same system I tried it out myself, and
voila...
valgrind gives no valuable information, except that it's a segfault:
sage: sage: a = var('a')
sage: sage
Ok then they didn't upgrade the valgrind package in the meantime.
I'm using Ubuntu myself and had the same problem, but I build my own
package with the latest source from svn. It worked for me
I can send it to you if you want, and you test it out.
maldun
On 7 Okt., 20:07, Johannes wrote:
> im s
I've created a trac ticket for this (http://trac.sagemath.org/
sage_trac/ticket/10100).
David
On 8 Oct, 08:16, Johannes wrote:
> that's the only test wich fails:
> The following tests failed:
> sage -t "devel/sage/sage/graphs/schnyder.py"
>
> I dont think that there is any connection to
that's the only test wich fails:
The following tests failed:
sage -t "devel/sage/sage/graphs/schnyder.py"
I dont think that there is any connection to my problem.
greatz Johannes
Am 07.10.2010 20:06, schrieb mhampton:
> Those commands work for me on linux (ubuntu 9.10, intel i7 860) a
On 10/ 7/10 08:02 PM, daveloeffler wrote:
For me it also crashes pretty consistently (using a build of Sage
4.6.alpha2 on 64-bit Ubuntu, which I know passes tests except some
clearly irrelevant known issues). It looks to me like the error isn't
in the real root finding code per se, but comes up w
For me it also crashes pretty consistently (using a build of Sage
4.6.alpha2 on 64-bit Ubuntu, which I know passes tests except some
clearly irrelevant known issues). It looks to me like the error isn't
in the real root finding code per se, but comes up when doing
"change_ring(RR)" on any polynomia
im sorry, but I cant install valgrind because it does not compile with
my glibc version.
Ubuntu 10.4 is comming with glib 2.10 and valgrind builds just with
glibc 2.2 up to 2.7
greatz
Am 07.10.2010 19:38, schrieb maldun:
> I would suggest to run sage with valgrind to get more information out
> of
Those commands work for me on linux (ubuntu 9.10, intel i7 860) and OS
X 10.6. Maybe you could run all the standard tests for sage (sage -t
$SAGE_ROOT/devel/sage/sage), that might help narrow the problem down.
-M. Hampton
> On 7 Okt., 17:31, Johannes wrote:
>
> > Hi list,
> > i got my sage cras
I would suggest to run sage with valgrind to get more information out
of your error messages.
On 7 Okt., 17:31, Johannes wrote:
> Hi list,
> i got my sage crashed once again:
>
> sage: a,b,c= var('a,b,c')
> sage: mprime = matrix([[01,b+1,2],[a+1,2,1],[2,1,c+1]])
> sage: cp = mprime.charpoly()
> s
16 matches
Mail list logo
