Bug? in Maxima 5.19.1 "Control stack guard page temporarily disabled"

On Tuesday 25 August 2009, Stefano Ferri wrote:
> I have the same issue, but having a Maxima version compiled with CLISP I
> get a stack overflow and Maxima exits. Anyway, the bug should have already
> been fixed in CVS version of Maxima, see
>
> https://sourceforge.net/tracker/?func=detail&atid=104933&aid=2843628&group_
>id=4933

Could someone (Dieter?) please point me to the location of the two patches
mentioned in the url above.

I have a very slow internet connection and I don't want to download
another 2-3 hours an archive like maxima-5.19.1.tar.gz

Why aren't there any release patch files on the sourceforge server?
the patch file (gzip compressed) between 5.17.1 and 5.19.1 would have been 
smaller than 2 Megs.

Andre


>
> I reported this bug but problems were already known.
> With your code, I get the same errors reported there.
>
>
>
> (%i1) build_info();
>
> Maxima version: 5.19.1
> Maxima build date: 23:43 8/24/2009
> host type: i486-slackware-linux-gnu
> lisp-implementation-type: CLISP
> lisp-implementation-version: 2.46 (2008-07-02) (built 3430478578) (memory
> 3460139030)
>
>
> Stefano
>
> In data luned? 24 agosto 2009 22:23:12, andre maute ha scritto:
> : > The following code snippet works flawlessly
> >
> > in Maxima 5.17.1 under a recent Ubuntu installation,
> > but not in Maxima 5.19.1
> >
> > ----------------------------------------------------
> > display2d : false;
> >
> > my_f(x) := block(
> >
> >         [res,t],
> >         res : integrate(1,t,-1,x),
> >         return(res)
> >
> > )$
> >
> > fy : my_f(y[2]);
> > ----------------------------------------------------
> >
> > here the output with maxima 5.17.1
> > ----------------------------------------------------
> > $ maxima -b stackbug3.max
> > Maxima 5.17.1 http://maxima.sourceforge.net
> > Using Lisp SBCL 1.0.18.debian
> > Distributed under the GNU Public License. See the file COPYING.
> > Dedicated to the memory of William Schelter.
> > The function bug_report() provides bug reporting information.
> > (%i1)                        batch(stackbug3.max)
> >
> > batching /home/user/tmp/stackbug3.max
> > (%i2)                          display2d : false
> > (%o2) false
> > (%i3) my_f(x):=block([res,t],res:integrate(1,t,-1,x),return(res))
> > (%i4) fy:my_f(y[2])
> > (%o4) y[2]+1
> > ----------------------------------------------------
> >
> > here the output with maxima 5.19.1
> > ----------------------------------------------------
> > $ maxima -b stackbug3.max
> > http://maxima.sourceforge.net
> > Using Lisp SBCL 1.0.18.debian
> > Distributed under the GNU Public License. See the file COPYING.
> > Dedicated to the memory of William Schelter.
> > The function bug_report() provides bug reporting information.
> > (%i1)                        batch(stackbug3.max)
> >
> > batching /home/user/tmp/stackbug3.max
> > (%i2)                          display2d : false
> > (%o2) false
> > (%i3) my_f(x):=block([res,t],res:integrate(1,t,-1,x),return(res))
> > (%i4) fy:my_f(y[2])
> > Control stack guard page temporarily disabled: proceed with caution
> > Maxima encountered a Lisp error:
> >
> >  Control stack exhausted (no more space for function call frames).
> > This is probably due to heavily nested or infinitely recursive function
> > calls, or a tail call that SBCL cannot or has not optimized away.
> >
> > PROCEED WITH CAUTION.
> >
> > Automatically continuing.
> > To reenable the Lisp debugger set *debugger-hook* to nil.
> > Control stack guard page temporarily disabled: proceed with caution
> > Maxima encountered a Lisp error:
> >
> >  Control stack exhausted (no more space for function call frames).
> > This is probably due to heavily nested or infinitely recursive function
> > calls, or a tail call that SBCL cannot or has not optimized away.
> >
> > PROCEED WITH CAUTION.
> >
> > Automatically continuing.
> > To reenable the Lisp debugger set *debugger-hook* to nil.
> > Control stack guard page temporarily disabled: proceed with caution
> > Maxima encountered a Lisp error:
> >
> >  Control stack exhausted (no more space for function call frames).
> > This is probably due to heavily nested or infinitely recursive function
> > calls, or a tail call that SBCL cannot or has not optimized away.
> >
> > PROCEED WITH CAUTION.
> >
> > Automatically continuing.
> > To reenable the Lisp debugger set *debugger-hook* to nil.
> > (%o5) "/home/user/tmp/stackbug3.max"
> > ----------------------------------------------------
> >
> > I have updated after a suggestion from Dieter Kaiser,
> > who had mentioned that a bug I had encountered,
> > had been fixed in Maxima 5.19.1
> >
> > Andre