Bug#593548: wxaxima loses connection to maxima for long connection
Frank S. Thomas
fst at debian.org
Sat Sep 24 10:40:01 UTC 2011
tags 593548 + unreproducible moreinfo
thanks
On Thursday 19 August 2010 17:13:13 Julian Andres Klode wrote:
> On Do, 2010-08-19 at 12:01 +0200, Frank S. Thomas wrote:
> > I've tried to reproduce this and this is what I got after some minutes:
> > | (%i1) sum(1/i, i, 1, 10^6);
> > |
> > | Maxima encountered a Lisp error:
> > | Error in FORMAT [or a callee]: Value stack overflow.
> > |
> > | Automatically continuing.
> > | To enable the Lisp debugger set *debugger-hook* to nil.
> >
> > This doesn't look like wxMaxima looses the connection to Maxima, so could
> > you please explain in more detail what happens in your case.
>
> For me:
>
> maxima: the command runs 14 minutes and prints a result
> wxmaxima gives CLIENT: Lost socket connection ...
> Restart Maxima with 'Maxima->Restart Maxima'.
> (after 10-20 seconds)
Since I got a value stack overflow in my first attempt to reproduce this bug,
I just tried to reproduce it again with a convergent series and wxMaxima
11.08.0:
| float(sum(1/i^2, i, 1, 10^3)); time(%);
| 1.64393456668156
| [0.02]
|
| float(sum(1/i^2, i, 1, 10^4)); time(%);
| 1.64483407184806
| [0.68]
|
| float(sum(1/i^2, i, 1, 10^5)); time(%);
| 1.644924066898226
| [43.57]
|
| float(sum(1/i^2, i, 1, 10^6)); time(%);
| 1.644933066848727
| [4146.08]
|
| ? time;
| -- Function: time (%o1, %o2, %o3, ...)
|
| Returns a list of the times, in seconds, taken to compute the
| output lines `%o1', `%o2', `%o3', .... The time returned is
| Maxima's estimate of the internal computation time, not the
| elapsed time.
So the last calculation lasted more than an hour and still succeeded. It would
be interesting to see if your bug is still present in the latest wxMaxima
version and if it is, whether it also happens with a convergent series.
Cheers,
Frank
More information about the debian-science-maintainers
mailing list