bugGNU Octave - Bugs: bug #56020, dbup and dbdown no longer work

 
 

bug #56020: dbup and dbdown no longer work

Submitter:  Guillaume <gyom>
Submitted:  Thu 28 Mar 2019 10:19:12 AM UTC
   
 
Category:  Interpreter Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Regression
Status:  Fixed Assigned to:  None
Originator Name:  Guillaume Open/Closed:  * Closed
Release:  * dev Operating System:  * Any
Fixed Release:  None Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Wed 10 Apr 2019 02:38:33 PM UTC, comment #5: 

Closing as fixed.  If there are other problems we can handle them in a separate report.

John W. Eaton <jwe>
Group administrator
Wed 10 Apr 2019 02:03:30 PM UTC, comment #4: 

I confirm it now works again.  Thank you!

Guillaume <gyom>
Wed 10 Apr 2019 01:23:12 PM UTC, comment #3: 

I pushed the following changeset:

http://hg.savannah.gnu.org/hgweb/octave/rev/8408acb7ca4f

It seems to work for me now.

John W. Eaton <jwe>
Group administrator
Thu 28 Mar 2019 05:43:37 PM UTC, comment #2: 

Yeah, I definitely broke it.  I need to think about the proper way for the debugger to move around in the call stack.  I thought it was working, but it is definitely completely broken.

John W. Eaton <jwe>
Group administrator
Thu 28 Mar 2019 03:19:39 PM UTC, comment #1: 

Confirmed.  This is a regression from 5.1.0.  I'm sure it has to do with the extensive rework of the symbol table that jwe has been undertaking.

Rik <rik5>
Group administrator
Thu 28 Mar 2019 10:19:12 AM UTC, original submission:  

In debugging mode, dbup and dbdown do not seem to work as expected. In this example:


%%%%%%%% testdb.m %%%%%%%%
function testdb
  val = 0;
  a;
end

function a
  val = 1;
  b;
end

function b
  val = 2;
  keyboard;
end


Octave's behavior is:


octave> testdb
stopped in /opt/octave/testdb.m at line 13
13:   keyboard;
debug> dbstack
stopped in:

  --> testdb>b at line 13 [/opt/octave/testdb.m]
      testdb>a at line 8 [/opt/octave/testdb.m]
        testdb at line 3 [/opt/octave/testdb.m]
debug> dbup
stopped in testdb>b at line 13 [/opt/octave/testdb.m]
debug> dbstack
stopped in:

  --> testdb>b at line 13 [/opt/octave/testdb.m]
      testdb>a at line 8 [/opt/octave/testdb.m]
        testdb at line 3 [/opt/octave/testdb.m]
debug> dbup
stopped in testdb>b at line 13 [/opt/octave/testdb.m]
debug> dbup
stopped in testdb>b at line 13 [/opt/octave/testdb.m]
debug> dbdown
error: dbdown: invalid stack frame
error: called from
    testdb>b at line 13 column 3
    testdb>a at line 8 column 3
    testdb at line 3 column 3


while in Matlab:


>> testdb
K>> dbstack
> In testdb>b (line 13)
  In testdb>a (line 8)
  In testdb (line 3)
K>> dbup
In workspace belonging to testdb>a (line 8)
K>> dbstack
  In testdb>b (line 13)
> In testdb>a (line 8)
  In testdb (line 3)
K>> dbup
In workspace belonging to testdb (line 3)
K>> dbstack
  In testdb>b (line 13)
  In testdb>a (line 8)
> In testdb (line 3)
K>> dbup
In base workspace.
K>> dbup
In base workspace.
K>> dbstack
  In testdb>b (line 13)
  In testdb>a (line 8)
  In testdb (line 3)
K>> dbdown
In workspace belonging to testdb (line 3)
K>> dbdown
In workspace belonging to testdb>a (line 8)
K>> dbdown
In workspace belonging to testdb>b (line 13)
K>> dbdown
In workspace belonging to testdb>b (line 13)


Guillaume <gyom>

 

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

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by jwe (Posted a comment)
  • -email is unavailable- added by rik5
  • -email is unavailable- added by rik5 (Posted a comment)
  • -email is unavailable- added by gyom (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 7 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2019-04-10 jwe StatusReady For Test Fixed
        Open/ClosedOpen Closed
    2019-04-10 jwe StatusConfirmed Ready For Test
    2019-03-28 rik5 Carbon-Copy- Added jwe
    2019-03-28 rik5 Item GroupUnexpected Error or Warning Regression
        StatusNone Confirmed
        Summarydbup and dbdown not working as expected dbup and dbdown no longer work

    Back to the top

    Powered by Savane 3.13-4b48.
    Corresponding source code