bugGNU Octave - Bugs: bug #53288, clear all clears breakpoints

 
 

bug #53288: clear all clears breakpoints

Submitter:  Melvin Robinson <melrobin>
Submitted:  Mon 05 Mar 2018 07:10:33 AM UTC
   
 
Category:  Interpreter Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Matlab Compatibility
Status:  Duplicate Assigned to:  None
Originator Name:  Open/Closed:  * Closed
Release:  * dev Operating System:  * GNU/Linux
Fixed Release:  None Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Mon 05 Mar 2018 11:24:40 AM UTC, comment #2: 

This is a duplicate of bug #53064.

Closing report.

Pantxo Diribarne <pantxo>
Group Member
Mon 05 Mar 2018 09:16:29 AM UTC, comment #1: 

For code, use verbatim-markup avoid interpretation as rich text:

https://savannah.gnu.org/cookbook/?func=detailitem&item_id=125

Confirmed here.  A simpler example is


octave:14> dbstatus
octave:15> dbstop print
ans =  316
octave:16> dbstatus
breakpoint in print at line 316
octave:17> clear all
octave:18> dbstatus
octave:19>


I suspect it has something to do with the function clearing as described in the doc:


     The following options are available in both long and short form

     '-all, -a'
          Clear all local and global user-defined variables and all
          functions from the symbol table.


Whatever it means for functions to be cleared from the symbol table might also be clearing breakpoints associated with those functions.  To illustrate, make the "clear" more specific:


octave:19> dbstatus
octave:20> dbstop print
ans =  316
octave:21> dbstop plot
ans =  211
octave:22> dbstatus
breakpoint in plot at line 211
breakpoint in print at line 316
octave:23> clear print
octave:24> dbstatus
breakpoint in plot at line 211
octave:25>


Dan Sebald <sebald>
Mon 05 Mar 2018 07:10:33 AM UTC, original submission:  

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

and the other for bar
[melrobin@scorpion 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.

Melvin Robinson <melrobin>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Digest:
   bug dependencies.

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by pantxo (Posted a comment)
  • -email is unavailable- added by sebald (Posted a comment)
  • -email is unavailable- added by melrobin (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only group members can vote.

     

    Follow 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2018-03-05 pantxo StatusNone Duplicate
        Open/ClosedOpen Closed
        Dependencies- Depends on bugs #53064

    Back to the top

    Powered by Savane 3.13-3cd0.
    Corresponding source code