[Top][All Lists]

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

Re: How to debug?

From: Ben Sapp
Subject: Re: How to debug?
Date: Thu, 6 Jun 2002 16:02:38 -0500

Hi Ben,  

I think you need to type 

dbg_set test 1

instead.  The ".m" is implied.   The debugger is not documented any where.  
As a matter of fact the names have recently changed to be more Matlab 
compatible.  So, for example, be warned that dbg_set is now dbstop in the 
CVS.   The best place to look is in the src/ file which all these 
functions are defined in(except for dbg_next and dbg_step mentioned below).  

Once you hit the breakpoint it is just as if you had put the keyborad command 
at that line in the function.  So, to continue you need to say "exit".  If 
you want to go to the next line in the same function you can type dbg_next.  
If you want to go to the next line in any function you can type dbg_step.   
Neither of these are documented at all.  That is, unlike dbg_set, help 
reveals nothing about these two functions.   

Good luck. 
Ben Sapp.  

On Thursday 06 June 2002 09:33 am, Ben Harris wrote:
> Hello folks,
> How do the debug commands work--dbg_set, dbg_where? Is there *any* online
> example of debugging in octave?
> I have tried unsuccessfully to debug under Octave 2.1.35 under Cygwin. For
> example, when I try to debug a test script using
> dbg_set('test.m','1')
> I get
> error: unable to find the function requested
> What am I doing wrong?
> Thanks in advance,
> Ben

Ben Sapp                         Los Alamos National Laboratory
email: <mailto:address@hidden>   Phone: (505)667-3277
Fax:   (505)665-7920             URL:

Octave is freely available under the terms of the GNU GPL.

Octave's home on the web:
How to fund new projects:
Subscription information:

reply via email to

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