From help-request at octave dot org Thu Feb 23 10:38:32 2006 Subject: Re: reursion debugging From: Joe Koski To: Octave Help Date: Thu, 23 Feb 2006 09:37:06 -0700 on 2/23/06 9:07 AM, Robert A. Macy at macy at california dot com wrote: > Not understanding debuggers, I always write my own. > > insert judicious code that writes important benchmark > values to a file for later review. Or display on the screen > and watch it go by > > - Robert - > Robert I agree with your philosophy of adding output when debugging octave code, but there is one additional point: Octave is usually very good about telling you where it quit and why. From that point of view, octave already has a built-in interactive debugger. Joe > > On Thu, 23 Feb 2006 15:43:42 +0100 > Gorazd Brumen wrote: >> Dear all, >> >> I have written a program, which is deeply recursive. >> There are around >> 4 functions with each calling some others recursively. >> >> Can somebody suggest me a good way to debug this, or more >> generally >> a good debugger for octave? >> >> >> Regards, >> GOrazd >> >> >> -- >> Gorazd Brumen >> Mail: brumen at isb dot unizh dot ch >> WWW: http://valjhun.fmf.uni-lj.si/~brumen >> PGP: Key at http://pgp.mit.edu, ID BCC93240 >> > > > > ------------------------------------------------------------- > Octave is freely available under the terms of the GNU GPL. > > Octave's home on the web: http://www.octave.org > How to fund new projects: http://www.octave.org/funding.html > Subscription information: http://www.octave.org/archive.html > ------------------------------------------------------------- > ------------------------------------------------------------- Octave is freely available under the terms of the GNU GPL. Octave's home on the web: http://www.octave.org How to fund new projects: http://www.octave.org/funding.html Subscription information: http://www.octave.org/archive.html -------------------------------------------------------------