bugGNU Octave - Bugs: bug #38556, dbwhere pointer is not updated...

 
 

bug #38556: dbwhere pointer is not updated during if/elseif or switch statements

Submitted by:  Rik <rik5>
Submitted on:  Wed 20 Mar 2013 05:24:46 PM UTC  
 
Category: InterpreterSeverity: 3 - Normal
Priority: 5 - NormalItem Group: Other
Status: FixedAssigned to: None
Originator Name: Open/Closed: Closed
Release: devOperating System: Any

Add a New Comment (Rich MarkupRich Markup):
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Mon 25 Mar 2013 11:22:10 PM UTC, comment #5:

Okay, now things seem back to normal with debugging. Closing this report again.

Rik <rik5>
Project Administrator
Mon 25 Mar 2013 10:58:00 PM UTC, comment #4:

I checked in the following changeset:

http://hg.savannah.gnu.org/hgweb/octave/rev/66330c7f6990

but I screwed up the commit message. It was supposed to be:

John W. Eaton <jwe>
Project Administrator
Fri 22 Mar 2013 03:32:46 PM UTC, comment #3:

Oops, I closed this too soon. The dbwhere pointer is succesfully updated. But, I now find that certain breakpoints are not hit.

One example is:

The hist command runs without hitting the breakpoint that was set.

Rik <rik5>
Project Administrator
Thu 21 Mar 2013 10:00:55 PM UTC, comment #2:

Everything appears to work well now. I'm closing this report.

Rik <rik5>
Project Administrator
Thu 21 Mar 2013 08:32:45 PM UTC, comment #1:

I checked in the following change:

http://hg.savannah.gnu.org/hgweb/octave/rev/fb27f1e08297

John W. Eaton <jwe>
Project Administrator
Wed 20 Mar 2013 05:24:46 PM UTC, original submission:

The current line being executed during debugging is available by calling dbwhere() and is also printed out at the debug prompt. The line number is not accurate if the statement being debugged is an "if" or "switch" statement. Instead of advancing to the next branch of an if/elseif tree the pointer remains stuck at the first line containing the "if" statement. A similar thing happens with switch statements where the pointer remains stuck at the line containing the "switch" statement and each dbnext causes the next "case" to be evaluated.

Sample code uses the attached dbgtst.m file.

Example:

Rik <rik5>
Project Administrator

 

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

Attach File(s):
   
   
Comment:
   

Attached Files
file #27638:  dbgtst.m added by rik5 (920B - text/x-octave)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by jwe (Posted a comment)
  • -unavailable- added by rik5 (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only project members can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 5 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Mon 25 Mar 2013 11:22:10 PM UTCrik5Open/ClosedOpen=>Closed
    Fri 22 Mar 2013 03:32:46 PM UTCrik5Open/ClosedClosed=>Open
    Thu 21 Mar 2013 10:00:55 PM UTCrik5StatusNone=>Fixed
      Open/ClosedOpen=>Closed
    Wed 20 Mar 2013 05:24:47 PM UTCrik5Attached File-=>Added dbgtst.m, #27638

    Back to the top


    Powered by Savane 3.1-cleanup