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 numbers or a call of a particular function. This will make it very difficult to troubleshoot, as simplifying the worksheet might make the error go away. I republished the slightly modified worksheet here, FYI: https://sagenb.kaist.ac.kr:8066/home/pub/60 Any idea how to shed more light into this?
Cheers Stan On Friday, March 29, 2013 6:23:27 PM UTC+1, kcrisman wrote: > > > > 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, this error is now reproducible, as in >> it happens at the same point every time now. Maybe it is an error in my >> code after all... >> > > You definitely use Maxima simplification a few times, but it doesn't > appear to intersect with the code that is repeated so often (fun_dynamics > etc.). Hmm. If you could try to remove a lot of that stuff it would be > really helpful; that is a very impressively long worksheet! > -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-support?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
