help-octave
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: how to debug octave code?


From: frank wang
Subject: Re: how to debug octave code?
Date: Tue, 22 Aug 2006 18:42:10 -0700

I have found the equivalent debug command in octave. Theny are dbg_cont, dbg_step, dbg_next.
 
Since I could not solve the problem that octave does not load the data file in, I have not tried these command yet.
 
 
Thanks
 
Frank

 
On 8/18/06, Robert A. Macy <address@hidden> wrote:
Frank,

I highly recommend using "homemade" techniques, like
temporarily print out a variable as it goes by.  In other
words, simply write your own debug sequences.

Lace your code with small pieces that write to file, sets
of variables, or single variable values.

Takes some thought process to figure out ways to do it, but
you gain more control over your program that way.  You
don't become reliant on "debug" features that may, or may
not, do what they claim.

For example, to debug function code where the variables are
erased when exiting the function, I write variables to a
file for later review, or simply single lines to the
monitor to watch as they go by.

Since octave is so modular, allowing you to write pieces of
code, anything more complex isn't realy required [to me]

                - Robert -

On Fri, 18 Aug 2006 09:29:30 -0700
"frank wang" <address@hidden > wrote:
> Hi,
>
> While porting my project, I found it is very difficult to
> debug the code. I
> can set break point in octave, however, after it breaks
> there, how can I
> single step? How can I continue to run? The debug command
> I found in octave
> are dbstop, dbwhere, dbstatus, dbclear. None of them will
> provide efficient
> debugging.
>
> Thanks
>
> Frank



reply via email to

[Prev in Thread] Current Thread [Next in Thread]