Re: [sage-support] Re: Bug in solve?

> > >> Only 2 years later, and I found a way around segmentation faults due to > >> memory problems. It seems that my looping functions fill up memory over > time > >> and lead to segmentation faults at random stages. I now define such > >> functions using the @fork decorator and then they don

Re: [sage-support] Re: Bug in solve?

On Wed, Jan 7, 2015 at 8:34 AM, kcrisman wrote: > >> Only 2 years later, and I found a way around segmentation faults due to >> memory problems. It seems that my looping functions fill up memory over time >> and lead to segmentation faults at random stages. I now define such >> functions using the

[sage-support] Re: Bug in solve?

> Only 2 years later, and I found a way around segmentation faults due to > memory problems. It seems that my looping functions fill up memory over > time and lead to segmentation faults at random stages. I now define such > functions using the @fork decorator and then they don't seem to cause

[sage-support] Re: Bug in solve?

Only 2 years later, and I found a way around segmentation faults due to memory problems. It seems that my looping functions fill up memory over time and lead to segmentation faults at random stages. I now define such functions using the @fork decorator and then they don't seem to cause crashes

[sage-support] Re: Bug in solve?

I just found out that adding an additional print command in fun_dynamics makes the crash move to a different position. The last number printed was 354 before, now it is 88 a lot further down the track. So it seems indeed to be a matter of filling up memory, and not a particular combination of n

[sage-support] Re: Bug in solve?

On Friday, March 29, 2013 12:39:48 PM UTC-4, Stan Schymanski wrote: > > Thanks for offering to look into it, kcrisman. > I wasn't able to isolate the error yet, but I uploaded a slightly trimmed > worksheet here: > https://sagenb.kaist.ac.kr:8066/home/pub/59 > Contrary to my previous impression

[sage-support] Re: Bug in solve?

Thanks for offering to look into it, kcrisman. I wasn't able to isolate the error yet, but I uploaded a slightly trimmed worksheet here: https://sagenb.kaist.ac.kr:8066/home/pub/59 Contrary to my previous impression, this error is now reproducible, as in it happens at the same point every time n

[sage-support] Re: Bug in solve?

Hi Jan, I did compile from source on my local laptop. Here is what I got when trying sage -gdb: sage -gdb -- | Sage Version 5.8, Release Date: 2013-03-15 | | Type "notebook()" for the browser-based note

[sage-support] Re: Bug in solve?

On Friday, March 29, 2013 6:14:21 AM UTC-4, Stan Schymanski wrote: > > Using 5.8 in Ubuntu 12.10, I get the same segmentation fault message in a > looping code without involving any solve() command. I am just using a > series of equations to calculate different values of variables saved in a >

Re: [sage-support] Re: Bug in solve?

Hi Stan, Did you download * sage-5.8-linux-64bit-ubuntu_12.04.2_lts-x86_64-Linux.tar.lzma* and untar that? That is not a from-source compile. You can run sage -gd

[sage-support] Re: Bug in solve?

Using 5.8 in Ubuntu 12.10, I get the same segmentation fault message in a looping code without involving any solve() command. I am just using a series of equations to calculate different values of variables saved in a dictionary ("vdict") and substitute those in the next equations, e.g.: vdict[

[sage-support] Re: Bug in solve?

This seems ECL-specific. A GCL-based Maxima installation does not encounter this (and does not solve the problem either) : Maxima 5.29.1 http://maxima.sourceforge.net using Lisp GNU Common Lisp (GCL) GCL 2.6.7 (a.k.a. GCL) Distributed under the GNU Public License. See the file COPYING. Dedicated t

Re: [sage-support] Re: Bug in solve?

Hi On 25 February 2013 01:06, Robert Dodier wrote: > Looks like a stack overflow in to_poly_solve -- I didn't go farther. Can > someone please submit a bug report. http://sourceforge.net/p/maxima/bugs > https://sourceforge.net/p/maxima/bugs/2553/ Regards, Jan -- .~. /V\ Jan Groenewal

[sage-support] Re: Bug in solve?

On 2013-02-24, Rolandb wrote: > Using 5.7 in Windows 64, I got the following message: > > solution=solve([(a*x+b*y)*x*y/c==1,3*log(a + b + c) - > log(27*a*b*x*y)],x,y,solution_dict=True) > for sol in solution: show(sol) > ;;; Detected access to protected memory, also kwown as 'bus or > segmen

[sage-support] Re: Bug in solve?

The same results also happen in Sage 4.7 on 64 bit Debian. var ('P X Y') solve ([(1/2) == -1/2*(2*P - 1)/Y + P/X, Y == 2*P*X/(2*P + 1), Y == P + 1/2], P,X,Y) On Jul 29, 10:52 pm, maor wrote: > I tried to solve the following simple 3 equations with 3 variables: > > sage: var ('P X Y') > (P, X, Y)

[sage-support] Re: bug in solve()?

The callable symbolic function is a red herring. The problem arises when solving one equation for one variable and using solution_dict=True (see below). Alex -- | Sage Version 3.4.1, Release Date: 2009-04-21 | | Type notebook()