[Octave-bug-tracker] [bug #53288] clear all clears breakpoints

[Melvin Robinson]

URL:
  <http://savannah.gnu.org/bugs/?53288>

                 Summary: clear all clears breakpoints
                 Project: GNU Octave
            Submitted by: melrobin
            Submitted on: Mon 05 Mar 2018 07:10:33 AM UTC
                Category: Interpreter
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Matlab Compatibility
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: GNU/Linux

    _______________________________________________________

Details:

Simple functions illustrate the problem:
One for foo
address@hidden convert_to_python]$ cat foo.m
clear all
a=bar_m(7,17);
a

and the other for bar
address@hidden convert_to_python]$ cat bar_m.m
function Y=bar_m(x,y)
% Split Bregman Anisotropic Total Variation Denoising
%
%   u = arg min_u 1/2||u-g||_2^2 + mu*ATV(u)
%
%   g : noisy image
%   mu: regularisation parameter
%   u : denoised image
%
% Refs:

   Y=2*x*y;

Type dbstop bar_m <enter> followed by foo <enter> and Octave ignores the
breakpoint.  Remove the "clear all" and Octave correctly enters debug mode.

Matlab enters debug mode regardless of the presence of "clear all".  

This may be more than a Matlab compatibility problem.  I am not sure how to
make any further progress in tracking down what is happening.




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?53288>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/