Re: solve test bug on GCL



Hi,

I'm glad Vadim pinned down this problem. It has been bothering me for a
while. I should warn everyone that I followed Vadim's hint and changed
the sloop variable from "v" to "testv" in the current CVS version as of
two days ago. It's only a workaround. I hope the real problem can be
identified. In order to do so, however, you will have to change the loop
variable back to "v" if you are using the current CVS version.

--Jim

On Fri, 2002-03-08 at 10:29, Camm Maguire wrote:
> Greetings!
> 
> "Vadim V. Zhytnikov" <vvzhy@mail.ru> writes:
> 
> > This is a multi-part message in MIME format.
> > --------------DCA8AA4BB1B26CA471011469
> > Content-Type: text/plain; charset=koi8-r
> > Content-Transfer-Encoding: 7bit
> > 
> > Greetings!
> > 
> > Finally I located the problem with solve test
> > on GCL Maxima build with new build system.
> 
> Does this error disappear with the old build system?
> 
> > If you load("test.lisp"); the following file
> > -------- tests.lisp ---------
> > (sloop for v in '("rtest.mac")
> >   do
> >   (test-batch v)
> > )
> > -----------------------------
> > with
> > ------- rtest.mac ----------
> > W:SOLVE([4*X^2-Y^2 = 12,X*Y-X = 2],[X,Y]);
> > [[X = 2,Y = 2],
> >  [X = 0.5202594388652008*%I-0.1331240357358706,
> >   Y = 0.07678378523787777-3.608003221870287*%I],
> >  [X = -0.5202594388652008*%I-0.1331240357358706,
> >   Y = 3.608003221870287*%I+0.07678378523787777],
> >  [X = -1.733751846381093,Y = -0.1535675710019696]];
> > -----------------------------
> > in GCL Maxima you will get an error.
> > But it is enough to change sloop variable v
> > to something different to get correct answer!
> > On Clisp everything works fine independently
> > on sloop variable name.
> > 
> 
> Well, unfortunately, I suspect gcl here.  Which version?  What about
> different input functions?  Can you go through the lisp debugger and
> isolate the lisp error?  I'd really appreciate it if you could get
> this into a form where a simple (as possible) input file into gcl
> shows the mistake.  Otherwise, we can of course build the gcl with -g
> and step through the stack in gdb, but I'm sure its quite huge.
> 
> > I'm perfectly sure that the problem has nothing to do
> > with recent solve changes. It is not clear yet
> > which part is to be blamed for the problem -
> > new build system or GCL. The case require
> > more thorough testing.
> 
> Thanks again for your work here, Vadim!
> 
> > 
> > Vadim
> > 
> > 
> > 
> > --
> > 
> > [ Vadim V. Zhytnikov  <vvzhy@mail.ru>  <vvzhy@td.lpi.ac.ru> ]
> > 
> > 
> > --------------DCA8AA4BB1B26CA471011469
> > Content-Type: application/x-gzip;
> >  name="solve.tar.gz"
> > Content-Transfer-Encoding: base64
> > Content-Disposition: inline;
> >  filename="solve.tar.gz"
> > 
> > H4sIAM/8eTwAA+3UXWvCMBQG4N6uvyIIY62z5SQnX052uYvBYBeDrUUUnG5M0Cna+fsXKzgG
> > buKF+4D3uUjT9JDTkJxUT8sqn4yX8+h4SBJZrSMKnDWfnmtSUUROs2WnNXOIl45lJOiI/7T1
> > tqwGCyGi1WA0nn4Tt+/7P5UsJ7PZXDzPFmIlxq/iLGksqvWZmA6GjTQ+EaNZaJL1UPY4qIYv
> > YpXGafyl314PHGa72UfMsa/+tVWb+leGnLR1/UuF+v8JDxd3tzf3V0lXN4u+ysq+EpdCqlbR
> > LLMidFWv1S1aZS/txN1uPdAqN8OxqN8pN4qUaWv23oYu+ebpdUa5ZJZKExvHxjuyIV6UdXzY
> > e+fZeaNC44KMc0ueiJWSIVR5F6bYJsgOzbBrtvMdaT8yyNwxOyO9tuwltble4zqFYWOdceEA
> > y7Zt216vgxsOAAAAAAAAAAAAAAAAAAAA/ph3Wq1t4QAoAAA=
> > --------------DCA8AA4BB1B26CA471011469--
> > 
> > 
> > 
> > 
> 
> -- 
> Camm Maguire			     			camm@enhanced.com
> ==========================================================================
> "The earth is but one country, and mankind its citizens."  --  Baha'u'llah
> _______________________________________________
> Maxima mailing list
> Maxima@www.math.utexas.edu
> http://www.math.utexas.edu/mailman/listinfo/maxima