help-octave
[Top][All Lists]
Advanced

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

dbstatus with no argument only returns local breakpoints


From: Jérôme
Subject: dbstatus with no argument only returns local breakpoints
Date: Tue, 11 Feb 2014 11:09:35 +0100
User-agent: Roundcube Webmail/0.9.5

Hi all.

The doc for dbstatus says :

http://octave.sourceforge.net/octave/function/dbstatus.html

"When called with no input or output arguments, print the list of all
functions with breakpoints and the line numbers where those breakpoints
are set. If a function name func is specified then only report
breakpoints for the named function. "

Unfortunately, when I call it from a .m file, it only returns the
breakpoints in this file.

------------------

Example :

Launch octave
> dbstop('file1', 1)
> dbstop('file2', 1)
> dbstatus:
breakpoints in file1 at line(s) 1.
breakpoints in file2 at line(s) 1.
> file2
stopped in /path/.../file2.m at line 1
1: my line 1
> dbstatus
breakpoints in file2 at line(s) 1.
> dbstatus('file1')
breakpoints in file1 at line(s) 1.

------------------

I'd expect dbstatus to return all breakpoints when called with no
argument, as the doc suggests. (Besides, it works like this with
Matlab.)

Is this a known issue ? Is there a workaround ? Should I file a bug ?

My objective is to save breakpoints while clearing variables :

s=dbstatus;
save('breakpoints.mat', 's');
clear all
close all
clc
load('breakpoints.mat', 's');
dbstop(s);

But it fails and what I understand is that when doing this in my main
file, only the breakpoints in this file are returned by dbstatus.

I'm using version 3.6.2, from Debian Wheezy. I didn't try later versions
because of dependencies, but I could if it was needed.

Thank you for any help.

-- 
Jérôme



reply via email to

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